 |
|
| If you can't view the Datasheet, Please click here to try to view without PDF Reader . |
|
|
|
| If you can't view the Datasheet, Please click here to try to view without PDF Reader . |
|
|
| Datasheet File OCR Text: |
| INTEGRATED CIRCUITS DATA SHEET PCD5013 FLEXTM roaming decoder II Product specification Supersedes data of 1999 Mar 15 File under Integrated Circuits, IC17 1999 Apr 12 Philips Semiconductors Product specification FLEXTM roaming decoder II CONTENTS 1 2 3 4 5 6 7 8 8.1 8.2 8.3 8.4 8.5 8.6 8.7 8.8 9 10 11 12 13 14 15 15.1 15.2 15.3 16 17 17.1 17.2 17.3 17.4 17.5 18 19 FEATURES APPLICATIONS GENERAL DESCRIPTION QUICK REFERENCE DATA ORDERING INFORMATION BLOCK DIAGRAM PINNING FUNCTIONAL DESCRIPTION General Clocking, reset and start-up Serial Peripheral Interface (SPI) Configuration and synchronisation Receiver control interface Configuration of the FLEXTM CAPCODE Call data packets Message reception LIMITING VALUES HANDLING THERMAL CHARACTERISTICS DC CHARACTERISTICS AC CHARACTERISTICS OSCILLATOR CHARACTERISTICS TEST AND APPLICATION INFORMATION FLEXTM protocol Example applications System block diagram PACKAGE OUTLINE SOLDERING Introduction to soldering surface mount packages Reflow soldering Wave soldering Manual soldering Suitability of surface mount IC packages for wave and reflow soldering methods DEFINITIONS LIFE SUPPORT APPLICATIONS PCD5013 1999 Apr 12 2 Philips Semiconductors Product specification FLEXTM roaming decoder II 1 FEATURES 2 APPLICATIONS PCD5013 * FLEXTM paging protocol decoder * 16 programmable user address words * 16 fixed temporary addresses * 16 operator messaging addresses * 1600, 3200 and 6400 bits/s decoding * Any-phase or single-phase decoding * Uses standard Serial Peripheral Interface (SPI) in slave mode * SSID and NID roaming support * Backward compatible to the standard and roaming FLEXTM decoder ICs * Allows low current power-down mode operation of host processor * Highly programmable receiver control * Real-time clock time base * FLEXTM fragmentation and group messaging support * Real-time clock over-the-air update support * Compatible with synthesized receivers * Low battery indication (external detector) * Low cost LQFP32 plastic package * Optional internal 4-level FSK demodulator and data slicer * Operates using a 76.8 or 160 kHz crystal * Very low power consumption * Operates at low supply voltage * Full support for revision 1.9 of the FLEXTM protocol. 4 QUICK REFERENCE DATA SYMBOL VDD IDD Tamb fEXTAL PARAMETER supply voltage supply current operating ambient temperature external clock frequency * Numeric FLEXTM pagers * Alphanumeric FLEXTM pagers * Roaming FLEXTM pagers * Remote metering * Car security systems * Personal digital assistants. 3 GENERAL DESCRIPTION This data sheet describes the operation of the PCD5013 integrated paging decoder. It is fully compatible with other FLEXchipTM ICs including the PCD5008. The PCD5013, also referred to as the decoder, simplifies implementation of a FLEXTM paging device, by being able to interface with several off-the-shelf paging receivers and host microcontrollers/processors. Its primary function is to process information received and demodulated from a FLEXTM radio paging channel, select messages addressed to the paging device and communicate the message information to the host. The PCD5013 fully supports the FLEXTM protocol (version G1.9) including all roaming aspects. Motorola FLEXstackTM software, installed on the product host processor, communicates with the PCD5013 and interprets the codewords that are passed to the host. The PCD5013 operates the paging receiver in an efficient power consumption mode and enables the host to operate in a low-power mode when monitoring a single channel for message information. CONDITIONS see Chapters 12 and 14 internal demodulator not in use internal demodulator in use MIN. 1.8 - -25 - - TYP. 2.2 6.0 +25 76.8 MAX. 3.6 - +70 - UNIT V A C kHz kHz 160.0 - 5 ORDERING INFORMATION TYPE NUMBER PACKAGE NAME LQFP32 DESCRIPTION plastic low profile quad flat package; 32 leads; body 7 x 7 x 1.4 mm VERSION SOT358-1 PCD5013H 1999 Apr 12 3 Philips Semiconductors Product specification FLEXTM roaming decoder II 6 BLOCK DIAGRAM PCD5013 handbook, full pagewidth S1 S2 S3 S4 S5 S6 S7 22 21 20 19 18 16 15 S0 INTERNAL CONTROL UNIT RECEIVER CONTROL PCD5013 S0/IFIN 23 IFIN DEMODULATOR & DATA SLICER EXTS0 EXTS1 SYMCLK OSCPD XTAL EXTAL 12 11 14 2 5 6 SYMBOL SYNC NOISE DETECTOR 3, 13 7, 29 VDD1, VDD2 VSS1, VSS2 76.8 kHz OR 160 kHz OSCILLATOR SYNC CORRELATOR 4 EXTERNAL CONTROL UNIT ERROR CORRECTOR 8 24 10 TEST2 TEST3 RESET LOBAT CLKOUT 32 CLOCK GENERATOR DEINTERLEAVER ADDRESS COMPARATOR/ CORRELATOR LOCAL MESSAGE FILTER CONTROL/STATUS REGISTERS SPI BUFFER SPI 26 READY 1 TOUT0 25 TOUT1 17 TOUT2 9 TOUT3 27 SS 28 30 31 MOSI SCK MISO MGR616 Fig.1 Functional block diagram for PCD5013 pager decoder. 1999 Apr 12 4 Philips Semiconductors Product specification FLEXTM roaming decoder II 7 PINNING SYMBOL TOUT0 OSCPD VDD1 TEST2 XTAL EXTAL VSS1 TEST3 TOUT3 LOBAT EXTS1 EXTS0 VDD2 SYMCLK S7 S6 TOUT2 S5 S4 S3 S2 S1 S0/IFIN RESET TOUT1 READY SS SCK VSS2 MOSI MISO CLKOUT Notes 1. These test outputs may be either left unconnected or connected to VSS in the application. PIN 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 I/O O I - I O I - I O I I I - O O O O O O O O O I/O I O O I I - I O O 3-state test output; note 1 DESCRIPTION PCD5013 internal oscillator power-down; connected to VSS when using the internal oscillator, connected to VDD when using an external source supply voltage manufacturing test mode input pin; has to be connected to VSS 76.8 or 160 kHz crystal oscillator output 76.8 or 160 kHz crystal oscillator input or external clock input ground supply manufacturing test mode input pin; has to be connected to VSS 3-state test output; note 1 low battery voltage detect input most significant bit (MSB) of the symbol currently being decoded least significant bit (LSB) of the symbol currently being decoded supply voltage recovered symbol clock output receiver control output port, 3-state receiver control output port, 3-state 3-state test output; note 1 receiver control output port, 3-state receiver control output port, 3-state receiver control output port, 3-state receiver control output port, 3-state receiver control output port, 3-state receiver control output port, 3-state when using external demodulator; limited IF input 455 or 140 kHz when using internal demodulator active LOW reset input 3-state test output; note 1 output driven LOW when the PCD5013 is ready for an SPI packet slave select input for SPI communications serial clock input for SPI communications ground supply data input for SPI communications data output for SPI communications, 3-state 38.4 kHz clock output (derived from 76.8 kHz oscillator); note 2 2. For a 160 kHz oscillator either a 38.4 or a 40 kHz output frequency can be selected. See Section 8.4.4. 1999 Apr 12 5 Philips Semiconductors Product specification FLEXTM roaming decoder II PCD5013 26 READY 25 TOUT1 handbook, full pagewidth 32 CLKOUT 31 MISO 30 MOSI 29 VSS2 28 SCK 27 SS TOUT0 OSCPD VDD1 TEST2 XTAL EXTAL VSS1 TEST3 1 2 3 4 24 RESET 23 S0/IFIN 22 S1 21 S2 PCD5013 5 6 7 8 20 S3 19 S4 18 S5 17 TOUT2 LOBAT 10 EXTS1 11 EXTS0 12 VDD2 13 SYMCLK 14 S7 15 TOUT3 S6 16 9 MGR619 Fig.2 Pin configuration. 1999 Apr 12 6 Philips Semiconductors Product specification FLEXTM roaming decoder II 8 8.1 FUNCTIONAL DESCRIPTION General PCD5013 host.The host can use receiver control lines which are not required by the receiver as expansion ports to control other peripheral devices. 8.2 8.2.1 Clocking, reset and start-up OSCILLATOR The PCD5013 simplifies implementation of a FLEXTM paging device by interfacing with off-the-shelf components such as a paging receiver and a microcontroller or microprocessor (called a host). The PCD5013 is fully compatible with FLEXstackTM software which provides a complete, platform independent, software driver for the PCD5013. The PCD5013 fully supports all aspects of the FLEXTM protocol (version G1.9), and can operate in either single-phase or any-phase mode. The PCD5013 supports FLEXTM dynamic grouping, allowing up to 16 temporary addresses to be enabled simultaneously. It is also capable of retrieving real time information from a FLEXTM channel. The PCD5013 connects to any receiver capable of providing a 2-bit digital signal. The PCD5013 operates the paging receiver in an efficient power consumption mode. The PCD5013 has 8 receiver control lines used for warming up, operating and shutting down a receiver in stages. The PCD5013 has the ability to detect a battery-low signal from an external detector during the receiver control sequences. The PCD5013 carries out the following functions: * Synchronises to a FLEXTM data stream * Processes received, demodulated information * Performs de-interleaving and error correction * Selects calls addressed to the paging device using up to 16 programmable addresses * Communicates the message information to the host. The PCD5013 interfaces to a host through a serial peripheral interface (SPI). The host can then interpret the message information in an appropriate manner (numeric, alphanumeric, binary, etc.). This function is provided by the FLEXstackTM software. When configured to use the internal demodulator, the PCD5013 connects to a receiver capable of generating a limited (i.e. 1-bit digitized) 455 or 140 kHz IF signal (IF frequency automatically detected). The PCD5013 enables the host to operate in a low-power mode when monitoring a single channel for message information. It has a 38.4 kHz clock output (40 kHz available when using the internal demodulator) capable of driving other devices, and has a 1-minute timer that offers low-power support for a real-time clock function on the The PCD5013 uses an inverting crystal oscillator. The clock signal for the internal circuitry is derived via an amplifier from the oscillator input pin EXTAL. Alternatively, an external clock signal can be fed in at input pin EXTAL. In this case the internal oscillator can be disabled by pulling the OSCPD input pin HIGH. This reduces current consumption and routes EXTAL directly to the internal clock signal. When using a crystal, an external feedback resistor and the load capacitances need to be connected to pins EXTAL and XTAL (Fig.19). See Chapter 14 for the recommended crystal parameters and the specification of the oscillator transconductance to guarantee correct start-up. The PCD5013 oscillator can operate at either 76.8 kHz or 160 kHz by selecting the appropriate crystal. The choice of frequency is determined by the setting of the IDE bit in the configuration packet; see Section 8.4.4. 8.2.2 RESET AND START-UP CONDITIONS The PCD5013 is reset by pulling the RESET input LOW. After releasing the RESET by pulling it HIGH, the PCD5013 counts 76 800 clock cycles (independent of the oscillator frequency) before pulling READY LOW to indicate that the decoder is ready for configuration via the SPI. See Fig.3 and Chapter 13 for the PCD5013 timing specifications when power is applied. See Fig.4 and Chapter 13 for the PCD5013 timing specifications when it is reset. After switch-on, the PCD5013 operates in Asynchronous mode, periodically sampling the channel for incoming data. As soon as data is detected, the PCD5013 maintains the receiver on to synchronize to the channel. Once the pager is synchronized to the channel it enters Synchronous mode, switching the receiver on only for the programmed frames. When the receiver is programmed for Roaming operation, the PCD5013 sends information which allows the host to calculate when to switch frequencies in a roaming network. 1999 Apr 12 7 Philips Semiconductors Product specification FLEXTM roaming decoder II PCD5013 handbook, full pagewidth VDD tstrt(osc) oscillator RESET READY tWUL(osc-READY) tHL(RESET-READY) th(rst) MBK031 Fig.3 Start-up timing. handbook, full pagewidth RESET tW(rst) READY tHL(RESET-READY) tLH(RESET-READY) MBK033 Fig.4 Reset timing. 1999 Apr 12 8 Philips Semiconductors Product specification FLEXTM roaming decoder II 8.3 8.3.1 Serial Peripheral Interface (SPI) GENERAL PCD5013 2. The PCD5013 indicates that it is ready to start the SPI transfer by driving the READY pin LOW. 3. The host clocks each of the 32 bits of the SPI packet by pulsing SCK. Both the host and the PCD5013 sample data on the rising edge of SCK. Packets are sent MSB first. 4. The PCD5013 pulls the READY line HIGH, to indicate that the transfer is complete. 5. The host waits until the READY line is pulled HIGH, then de-selects the PCD5013 SPI by driving the SS pin HIGH. 6. The first 5 steps are repeated for each additional packet. 8.3.4 SPI TRANSFER INITIATED BY THE DECODER All data communication between the PCD5013 and the host is done via the SPI using 32-bit data packets at data rates up to 1 Mbits/s. SPI transfers are full-duplex and can be initiated by either the host which acts as the SPI master providing the data clock for packet transfer, or the PCD5013 as an SPI slave. The host can send packets to configure or control the PCD5013 or a checksum packet to validate SPI communication (Section 8.4.2). The PCD5013 buffers data packets, relating to received data, into a 32 packet transmit buffer. The PCD5013 can send either a status packet, a part ID packet, or packets from the transmit buffer. In the event of a buffer overflow, the PCD5013 stops decoding and clears the transmit buffer. 8.3.2 SPI INTERCONNECT The following steps occur when the PCD5013 initiates an SPI packet transfer, see Fig.6 for event timings: 1. The PCD5013 initiates the SPI transfer by driving the READY pin LOW. 2. If the PCD5013 is not already selected, the host selects the PCD5013 SPI by driving the SS pin LOW. 3. The host clocks each of the 32 bits of the SPI packet by pulsing SCK. Both the host and the PCD5013 sample data on the rising edge of SCK. Packets are sent MSB first. 4. The PCD5013 pulls the READY line HIGH, to indicate that the transfer is complete. 5. The host may then either de-select the SPI interface of the PCD5013 (Fig.7) by driving the SS pin HIGH or maintain SS LOW to continue sending packets to the PCD5013. Connection on the PCD5013 consists of a READY pin and 4 SPI pins (SS, SCK, MOSI and MISO): READY: output signal; indicates that data is available from the PCD5013 SS: SPI select; used as PCD5013 chip select SCK: serial clock; output from the host used for clocking data MOSI: master output slave input; data output from the host MISO: master input slave output; data output from the PCD5013. 8.3.3 SPI TRANSFER INITIATED BY THE HOST The following steps occur when the host initiates an SPI packet transfer, see Fig.5 for event timings: 1. The host selects the PCD5013 by driving the SS pin LOW. 1999 Apr 12 9 Philips Semiconductors Product specification FLEXTM roaming decoder II PCD5013 handbook, full pagewidth SS (1) (5) READY (2) (4) SCK (3) MOSI D31 D1 D0 D31 D1 D0 D31 D1 D0 MISO Zo(off) D31 D1 D0 Zo(off) D31 D1 D0 Zo(off) D31 D1 D0 Zo(off) MGK262 Numbers within parenthesis refer to sequence numbers, see Section 8.3.3. Fig.5 Typical multiple SPI transfers initiated by the host. handbook, full pagewidth SS (2) (5) READY (1) (4) SCK (3) MOSI D31 D1 D0 D31 D1 D0 D31 D1 D0 MISO Zo(off) D31 D1 D0 Zo(off) D31 D1 D0 Zo(off) D31 D1 D0 Zo(off) MGK263 Numbers within parenthesis refer to sequence numbers, see Section 8.3.4. Fig.6 Typical multiple SPI transfers initiated by the PCD5013. 1999 Apr 12 10 Philips Semiconductors Product specification FLEXTM roaming decoder II PCD5013 handbook, full pagewidth SS READY SCK MOSI D31 D1 D0 D31 D1 D0 D31 D1 D0 MISO Zo(off) D31 D1 D0 D31 D1 D0 D31 D1 D0 MGK264 Fig.7 Multiple SPI transfers initiated by the PCD5013 with SS maintained LOW. 1999 Apr 12 11 Philips Semiconductors Product specification FLEXTM roaming decoder II 8.3.5 SPI PACKET FORMAT 8.3.6 SPI TIMING PCD5013 SPI data packets consist of an 8-bit ID (byte 3), followed by 24 bits of information (byte 2 to byte 0). See Table 1, note that bit 7 of byte 3 is the first bit on the bus. Table 1 BYTE 3 2 1 0 Packet bit assignments BIT 7 D31 D23 D15 D7 BIT 6 D30 D22 D14 D6 BIT 5 D29 D21 D13 D5 See Fig.8 and Chapter 13 for the timing specifications of the SPI. BIT 4 D28 D20 D12 D4 BIT 3 D27 D19 D11 D3 BIT 2 D26 D18 D10 D2 BIT 1 D25 D17 D9 D1 BIT 0 D24 D16 D8 D0 handbook, full pagewidth SS tSSH READY td(SS-READY) tLEAD2 tLEAD1 Tcy(SCK) tr tf tREADYH tLAG2 tLAG1 SCK tSCKL Zo(off) tSCKH D31 D0 tDOV th(o)(D) to(dis) MISO tACC(o) MOSI tsu(i)(D) D31 D0 MBK032 th(i)(D) Fig.8 SPI timing. 1999 Apr 12 12 Philips Semiconductors Product specification FLEXTM roaming decoder II 8.3.7 HOST-TO-DECODER PACKETS OVERVIEW PCD5013 This section summarises the packets which can be sent from the host to the decoder. Table 2 Host-to-decoder packet ID map2 PACKET ID (HEX) 00 01 02 03 04 05 06 07 to 0E 0F 10 11 12 13 14 15 16 17 18 19 1A 1B 1C to 1F 20 21 22 23 24 25 26 27 28 to 77 78 79 to 7F 80 81 82 1999 Apr 12 checksum configuration control all frame mode operator message address enable roaming control timing control reserved (host should never send) receiver line control receiver control configuration (off setting) receiver control configuration (warm-up 1 setting) receiver control configuration (warm-up 2 setting) receiver control configuration (warm-up 3 setting) receiver control configuration (warm-up 4 setting) receiver control configuration (warm-up 5 setting) receiver control configuration (3200 sps sync setting) receiver control configuration (1600 sps sync setting) receiver control configuration (3200 sps data setting) receiver control configuration (1600 sps data setting) receiver control configuration (shut-down 1 setting) receiver control configuration (shut-down 2 setting) special (ignored by decoder) frame assignment (frames 112 to 127) frame assignment (frames 96 to 111) frame assignment (frames 80 to 95) frame assignment (frames 64 to 79) frame assignment (frames 48 to 63) frame assignment (frames 32 to 47) frame assignment (frames 16 to 31) frame assignment (frames 0 to 15) reserved (host should never send) user address enable reserved (host should never send) user address assignment (user address 0) user address assignment (user address 1) user address assignment (user address 2) 13 TYPE 8.4.6 8.4.4 8.4.7 8.8.4 8.6.9 8.4.9 8.4.10 - 8.5.7 8.5.4 8.5.5.3 8.5.5.3 8.5.5.3 8.5.5.3 8.5.5.3 8.5.6.2 8.5.6.2 8.5.6.2 8.5.6.2 8.5.8.1 8.5.8.1 - 8.6.7 8.6.7 8.6.7 8.6.7 8.6.7 8.6.7 8.6.7 8.6.7 - 8.6.6 - 8.6.6 8.6.6 8.6.6 SECTION Philips Semiconductors Product specification FLEXTM roaming decoder II PCD5013 PACKET ID (HEX) 83 84 85 86 87 88 89 8A 8B 8C 8D 8E 8F 90 to FF 8.3.8 TYPE user address assignment (user address 3) user address assignment (user address 4) user address assignment (user address 5) user address assignment (user address 6) user address assignment (user address 7) user address assignment (user address 8) user address assignment (user address 9) user address assignment (user address 10) user address assignment (user address 11) user address assignment (user address 12) user address assignment (user address 13) user address assignment (user address 14) user address assignment (user address 15) reserved (host should never send) 8.6.6 8.6.6 8.6.6 8.6.6 8.6.6 8.6.6 8.6.6 8.6.6 8.6.6 8.6.6 8.6.6 8.6.6 8.6.6 - SECTION DECODER-TO-HOST PACKETS OVERVIEW This section summarises the packets which can be sent from the PCD5013 to the host (Table 3). Table 3 Decoder-to-host packet ID map PACKET ID (HEX) 00 01 02 to 57 58 to 5F 60 61 to 7D 7E 7F 80 to FE FF block information word address vector or message (ID is word number in frame) reserved roaming status reserved receiver shutdown status reserved part ID TYPE 8.7.9 8.7.2 8.7.3 and 8.7.8 - 8.4.13 - 8.4.12 8.4.11 - 8.4.5 SECTION 1999 Apr 12 14 Philips Semiconductors Product specification FLEXTM roaming decoder II 8.4 8.4.1 Configuration and synchronisation GENERAL PCD5013 sending a checksum packet for which the checksum value matches the checksum register. Checksum packets sent when the SPI transmit is enabled, are ignored by the PCD5013 irrespective of the value of the checksum packet data bits. Thus when the PCD5013 initiates an SPI transfer and the host has no data to send, the host should send the checksum packet so as not to disable the SPI transmit. The data in the checksum packet could be a null packet (32-bit stream of all zeros). Sending a packet other than the checksum packet when the SPI transmit is enabled causes the SPI transmit to be disabled until a checksum packet is sent with the correct value. Thus when the host re-configures the PCD5013 after a reset, the SPI transmit is disabled until the host sends a checksum packet at the end of the configuration data, with the checksum value equal to the result of XORing together the data bits of each of the configuring packets and the data bits of the part ID packet. If the SPI transmit is enabled and a receiver shutdown packet is pending, the receiver shutdown packet is sent. If there is no receiver shutdown packet pending, but there is a roaming status packet pending, the roaming status packet is sent. If neither the receiver shutdown packet nor the roaming status packet is pending and there is data in the transmit buffer, the PCD5013 initiates an SPI transfer sending a packet from its transmit buffer. The PCD5013 sends the status packet (which is not buffered) when the host initiates an SPI transfer and the transmit buffer is empty. After a reset, all configuration data has to be (re)loaded into the PCD5013 by the host using the SPI. PCD5013 features which do not change during operation are configured using the configuration packet (Section 8.4.4), the receiver control packets (Section 8.5) and the address configuration packets (Section 8.6). PCD5013 features which can be changed during operation are configured using the control packet. The checksum packet ensures proper communication between the host and the PCD5013. 8.4.2 SPI SECURITY ALGORITHM The PCD5013 provides a security algorithm to verify correct SPI operation (Figs 9 and 10). The PCD5013 maintains a checksum register equal to the result of XORing the 24 data bits of every packet it receives, except the checksum packet 00H and special packets 1CH to 1FH. When the PCD5013 is reset, the internal checksum register is initialized to the 24-bit part ID defined in the part ID packet. Immediately following a reset and whenever the host sends a packet other than a checksum packet, the SPI output of status and data (SPI transmit) is disabled. The PCD5013 then initiates SPI transfers continuously, sending the part ID packet (Section 8.4.5). Note that when SPI transmit is disabled all decoding and timing functions are unaffected. The SPI transmit can be enabled by handbook, full pagewidth PART ID REGISTER 32 RECEIVER SHUTDOWN REGISTER 32 ROAMING STATUS REGISTER 32 32 x 32 DATA PACKET FIFO TRANSMIT BUFFER 32 MUX 32 SPI TRANSMIT REGISTER MGR618 MISO STATUS REGISTER 32 SPI SECURITY ALGORITHM Fig.9 SPI transmit functional block diagram. 1999 Apr 12 15 Philips Semiconductors Product specification FLEXTM roaming decoder II PCD5013 handbook, full pagewidth reset PCD5013 disables SPI transmit PCD5013 initializes checksum register to part ID value PCD5013 initiates part ID packet PCD5013 waits for SPI packet from host Y checksum packet? N Y PCD5013 SPI transmit enabled? N packet data matches checksum register data? Y PCD5013 enables SPI transmit PCD5013 disables SPI transmit N PCD5013 sets checksum registers to the XOR of the packet data bits with the checksum register bits MGR617 Fig.10 SPI security algorithm. 1999 Apr 12 16 Philips Semiconductors Product specification FLEXTM roaming decoder II 8.4.3 CONFIGURATION SEQUENCE PCD5013 5. At the end of each packet the PCD5013 pulls the READY line HIGH, and then LOW again to indicate that packet processing is complete. 6. The host writes a control packet to enable FLEXTM decoding in the PCD5013 (Section 8.4.7). 7. The host writes a checksum packet to enable SPI data output by the PCD5013 (Section 8.4.2). 8. On recognising a SYNC word, the PCD5013 synchronises to the channel. 9. The PCD5013 initiates an SPI transfer writing the status packet, indicating that it is now in synchronous mode. A typical configuration and synchronisation sequence would be as follows, see Fig.11 for event timings: 1. The PCD5013 is reset by the host. 2. After 76800 clock cycles the PCD5013 interrupts the host to read the part ID by pulling the READY line LOW. 3. The host pulls SS LOW at the start of each SPI transfer and clocks out the part ID data. 4. The host configures the following aspects of PCD5013 operation: a) General configuration (Section 8.4.4) b) Receiver operation (Section 8.5) c) FLEXTM CAPCODE configuration (Section 8.6). The PCD5013 writes a part ID packet in response to each incoming packet. handbook, full pagewidth configuration packets (addresses, receiver etc.) control packet (6) checksum packet (7) SPI HOST-TO-DECODER partid packet (4) SPI DECODER-TO-HOST partid packet (4) RESET (1) (5) (5) (5) status packet (9) READY (2) SS (3) (8) FLEX DATASTREAM SYNC MBK097 Numbers within parenthesis refer to sequence numbers, see Section 8.4.3. Fig.11 Typical configuration and synchronization sequence. 1999 Apr 12 17 Philips Semiconductors Product specification FLEXTM roaming decoder II 8.4.4 CONFIGURATION PACKET (ID = 01H) PCD5013 SP: signal polarity (Tables 8, 5 and 6). These bits set the polarity of EXTS1 and EXTS0 input signals. The polarity of the EXTS1 and EXTS0 bits is determined by the receiver design. Value after reset = 0. Table 5 SP1 0 0 1 1 Table 6 EXTS1 1 1 0 0 Input signal polarity SIGNAL POLARITY SP0 0 1 0 1 EXTS1 normal normal inverted inverted EXTS0 normal inverted normal inverted The configuration packet defines a number of different configuration options for the PCD5013. The PCD5013 ignores this packet when decoding is enabled, i.e. the ON bit in the control packet is set (Table 12). DFC: disable fractional clock (Table 8). When this bit is set and IDE is set, the CLKOUT signal generates a 40 kHz signal (EXTAL divided-by-4). When this bit is cleared and IDE is set, the CLKOUT signal generates a 38.4 kHz signal (EXTAL fractionally divided by 256). This bit has no effect when IDE is cleared. Value after reset = 0. IDE: internal demodulator enable (Table 8). When this bit is set, the internal demodulator is enabled and the clock frequency at EXTAL is expected to be 160 kHz. When this bit is cleared, the internal demodulator is disabled and the clock frequency at EXTAL is expected to be 76.8 kHz. Value after reset = 0. OFD: oscillator frequency difference (Tables 4 and 8). These bits represent the maximum frequency difference between the 76.8 kHz oscillator (accounting for ageing, temperature variation, manufacturing tolerance etc.) and the worst case transmitter bit rate (specified as 25 parts per million (ppm) in the FLEXTM specification). For example, if the transmitter tolerance is 25 ppm and the 76.8 kHz oscillator tolerance is 140 ppm, the transmitter-oscillator frequency difference is 165 ppm and OFD should be cleared (300 ppm maximum). Value after reset = 0. Note that configuring a smaller frequency difference in this packet results in lower power consumption due to higher receiver battery save ratios. Table 4 OFD1 0 0 1 1 Oscillator frequency difference OFD0 0 1 0 1 FREQUENCY DIFFERENCE (ppm) 300 150 75 0 FLEXTM 4 level FSK modulation (SP = 00) EXTS0 0 1 1 0 DEVIATION (Hz) +4800 +1600 -1600 -4800 SME: synchronous mode enable (Table 8). When this bit is set, a status packet is sent automatically whenever the synchronous mode update (SMU) bit in the status packet is set. This happens whenever a change occurs in the synchronous mode (SM) status bit, which indicates that the decoder is synchronized to a FLEXTM data stream. The host can use the SM bit in the status packet as an in-range/out-of-range indication. Value after reset = 0. COD: clock output disable (Table 8). When this bit is cleared, a 38.4 or 40 kHz signal is output on the CLKOUT pin (depending on the values of IDE and DFC). When this bit is set, the CLKOUT pin is driven LOW. Value after reset = 0. * Setting and clearing this bit can cause pulses on the CLKOUT pin that are less than one half the 38.4 kHz period. * When the clock output is enabled and not set for intermittent operation (see ICO in this packet), the CLKOUT pin always outputs the clock signal even when the PCD5013 is in reset (as long as a clock signal is available to the PCD5013 oscillator). * When the PCD5013 is used in internal demodulator mode (i.e. uses a 160 kHz oscillator), the CLKOUT pin is 80 kHz from reset until the time the IDE bit is set. PCE: partial correlation enable (Table 8). When this bit is set, partial correlation of addresses is enabled. When partial correlation is enabled, the PCD5013 shuts down the receiver before the end of the last FLEXTM block which contains addresses if it can determine that none of the addresses in that FLEXTM block matches any enabled address in the PCD5013. When this bit is cleared, the receiver is controlled as in the PCD5008. Value after reset = 0. 1999 Apr 12 18 Philips Semiconductors Product specification FLEXTM roaming decoder II LBP: low battery polarity (Table 8). This bit defines the polarity of the PCD5013's LOBAT pin: When this bit is set, a HIGH at input LOBAT represents a low battery condition. The LB bit in the status packet is initialized to the inverse (i.e. inactive) value of the LBP bit when the PCD5013 is turned on (by setting the ON bit in the control packet). When the PCD5013 is turned on, the first low battery update in the status packet is sent to the host when a low battery condition is detected on the LOBAT pin. Value after reset = 0. MOT: maximum off time (Table 8). When this bit is set, the PCD5013 assumes that the service provider leaves up to 1 minute between transmitted frames. When this bit is clear, the PCD5013 assumes that there can be up to 4 minutes between transmitted frames. This bit has no effect if AST in the Timing Control Packet is non-zero. Value after reset = 0. MTE: minute timer enable (Table 8). When this bit is set, a status packet is sent at one minute intervals with the minute time-out (MT) bit in the status packet set. When this bit is clear, the internal 1-minute timer stops counting. See Section 8.4.8 for details of 1-minute timer operation. Note that the minute timer is not accurate using a 160 kHz oscillator until the IDE bit is set. Value after reset = 0. ICO: intermittent clock out (Table 8). When this bit is clear and COD is clear, a 38.4 or 40 kHz (depending on the values of IDE and DFC) signal is output on the CLKOUT pin. When this bit is set and COD is clear, the clock is only output on the CLKOUT pin while the receiver is not in the Off state. The clock is output for a few cycles before the receiver transitions from the off state and for a few cycles after the receiver transitions to the off state (this is to insure that the receiver receives enough clocks to detect and process the changes to and from the off state). The CLKOUT pin is driven LOW when it is not driving a clock. Table 8 BYTE 3 2 1 0 Configuration packet bit assignments BIT 7 0 0 0 SME BIT 6 0 DFC 0 MOT BIT 5 0 0 0 COD BIT 4 0 0 0 MTE BIT 3 0 0 0 LBP BIT 2 0 IDE PCE ICO PCD5013 Note that when the clock is automatically enabled and disabled (i.e. when ICO is set), the CLKOUT signal transitions are clean (i.e. no pulses less than half the clock period) when it transitions between no clock and clocked output. This bit has no effect when COD is set. Value after reset = 0. 8.4.5 PART ID PACKET (ID = FFH) The part ID packet is output by the PCD5013 SPI whenever the SPI transmit is disabled due to the checksum feature. The value of the part ID packet for the PCD5013 is FF000308H. MDL: model (Table 9). The PCD5013 model value is 0. CID: compatibility ID (Table 9). This value describes other parts with the same model number, which are compatible with this part. Table 7 BIT CID Compatibilities COMPATIBILITY VALUE FOR PCD5013 1 (true) 1 (true) 0 (false) CID0 Alphanumeric Decoder I CID1 Roaming Decoder I CID2 Numeric Decoder REV: revision (Table 9). This identifies the manufacturing version of the PCD5013. For the PCD5013 the value is 8. 8.4.6 CHECKSUM PACKET (ID = 00H) See Table 10 for checksum packet bit assignment. CV: checksum value (24 bits), see Section 8.4.2. BIT 1 0 OFD1 SP1 0 BIT 0 1 OFD0 SP0 0 1999 Apr 12 19 Philips Semiconductors Product specification FLEXTM roaming decoder II Table 9 BYTE 3 2 1 0 Part ID packet bit assignments BIT 7 1 MDL1 CID7 REV7 BIT 6 1 MDL0 CID6 REV6 BIT 5 1 CID13 CID5 REV5 BIT 4 1 CID12 CID4 REV4 BIT 3 1 CID11 CID3 REV3 BIT 2 1 CID10 CID2 REV2 PCD5013 BIT 1 1 CID9 CID1 REV1 BIT 0 1 CID8 CID0 REV0 Table 10 Checksum packet bit assignments BYTE 3 2 1 0 BIT 7 0 CV23 CV15 CV7 BIT 6 0 CV22 CV14 CV6 BIT 5 0 CV21 CV13 CV5 BIT 4 0 CV20 CV12 CV4 BIT 3 0 CV19 CV11 CV3 BIT 2 0 CV18 CV10 CV2 BIT 1 0 CV17 CV9 CV1 BIT 0 0 CV16 CV8 CV0 1999 Apr 12 20 Philips Semiconductors Product specification FLEXTM roaming decoder II 8.4.7 CONTROL PACKET (ID = 02H) PCD5013 SBI: send block information words (BIW) 2 to 4 (Table 12). When this bit is set, BIWs with time and date information and BIWs received in error are sent to the host, (Section 8.7.9). Value after reset = 0. MTC: minute timer clear (Table 12). Setting this bit causes the 1-minute timer to restart from 0 (Section 8.4.8). ON: turn on decoder (Table 12). When this bit is set, the PCD5013 decodes FLEXTM signals. If this bit is cleared, signal processing stops. However, to assure proper operation, the PCD5013 requires that it be set into asynchronous mode when turned off. To achieve that the following sequence must be used: 1. Send control packet with ON bit clear (decoder off) 2. Send control packet with ON bit set (decoder on) 3. Send control packet with ON bit clear (decoder off). Timing between these steps is specified below and is measured from the positive edge of the last clock of one packet to the positive edge of the last clock of the next packet. * The minimum time between steps 1 and 2 is the greater of 2 ms or the programmed shut-down time. The programmed shut-down time is the sum of all of the times programmed in the used receiver shut-down settings packets. * There is no maximum time between steps 1 and 2. * The minimum time between steps 2 and 3 is 2 ms. * The maximum time between steps 2 and 3 is the programmed warm-up time minus 2 ms. The programmed warm-up time is the sum of all the times programmed in the used receiver warm-up settings packets. EAE: end of addresses enable. When this bit is set, the EA bit in the Status Packet is PCD5013 set immediately after the PCD5013 decodes the last address word in the frame if any of the enabled PCD5013 addresses was detected in the frame. When this bit is cleared, the EA bit is never set. The control packet defines a number of different control bits for the PCD5013. FF: force frame 0 to 7 (Table 12). When set, each of these bits forces the PCD5013 to decode one of the FLEXTM frames 0 to 7 irrespective of the system collapse value (for details of collapse values see Section 8.6.2). For example, if the system collapse causes the PCD5013 to decode frames 0, 32, 64 and 96, setting FF2 causes the PCD5013 to also decode FLEXTM frame 2. This may be used to acquire transmitted time information or channel attributes (e.g. Local ID). Value after reset = 0. SPM: single phase mode (Table 12). When this bit is set, the PCD5013 decodes only one of the transmitted phases. When this bit is clear, the PCD5013 decodes all transmitted phases. This value is determined by the CAPCODE (Section 8.6). A change to this bit while the PCD5013 is on does not take effect until the next block 0 of a frame. Value after reset = 0. PS: phase select (Tables 11 and 12). When the SPM bit is set, these bits define which phase the PCD5013 shall decode. This value is determined by the CAPCODE (Section 8.6). A change to these bits, while the PCD5013 is on, does not take effect until the next block 0 of a frame. Value after reset = 0. Table 11 Phase selection (by PS bits) DECODED PHASE (BASED ON FLEXTM DATA RATE) 1600 bits/s 3200 bits/s 6400 bits/s 0 0 1 1 0 1 0 1 A A A A A A C C A B C D PS1 PS0 Table 12 Control packet bit assignments BYTE 3 2 1 0 BIT 7 0 FF7 0 0 BIT 6 0 FF6 SPM SBI BIT 5 0 FF5 PS1 0 BIT 4 0 FF4 PS0 MTC BIT 3 0 FF3 0 0 BIT 2 0 FF2 0 0 BIT 1 1 FF1 0 EAE BIT 0 0 FF0 0 ON 1999 Apr 12 21 Philips Semiconductors Product specification FLEXTM roaming decoder II 8.4.8 OPERATING THE 1-MINUTE TIMER PCD5013 If the PCD5013 is in asynchronous mode when this occurs, it stays in asynchronous mode and end the A-word search. This is done to avoid synchronizing to a non-roaming channel when searching for roaming channels. This bit is set and cleared by the host. Value after reset = 0. MCM: manual collapse mode (Table 13). When this bit is set, the PCD5013 behaves as if the system collapse was 7. The PCD5013 does not apply the received system collapse to the AF bits. When this bit is set, the received system collapse is reported to the host via SCU and RSC in the Roaming Status Packet. This is so the host can modify the AF bits based on the system collapse of the channel. This bit is set and cleared by the host. Value after reset = 0. IS1: invert EXTS1 (Table 13). Setting this bit inverts the expected polarity of the EXTS1 pin from the way it is configured by SP 1 in the Configuration Packet (e.g. if both IS1 and SP 1 are set, the polarity of the EXTS1 pin is untouched). This bit is intended to be changed when a change in a channel changes the polarity of the received signal. This bit is set and cleared by the host. This bit has the equivalent effect when using the internal demodulator. Value after reset = 0. SDF: stop decoding frame (Table 13). Setting this bit causes the PCD5013 to stop decoding a frame without losing frame synchronization. This bit is set by the host, and cleared by the PCD5013 once it has been processed. The packet with the SDF bit set must be sent after receiving the status packet with EA bit set. It must be sent within 40 ms of the end of block in which the PCD5013 set the EA bit. Value after reset = 0. RSP: receiver shutdown packet enable (Table 13). When this bit is set, a Receiver Shutdown Packet is sent whenever the receiver is shut down. The receiver shutdown packet informs the host that the receiver shutdown, and gives the time period before the PCD5013 automatically warms the receiver back up. Value after reset = 0. The PCD5013 provides a 1-minute timer which allows the host to implement a time-of-day function while maintaining low-power operation. The 1-minute timer is enabled using the MTE bit in the configuration packet (Section 8.4.4). When the 1-minute timer is enabled, a status packet is sent at 1-minute intervals with the MT bit set (Section 8.4.11). When the MTE bit is clear, the internal 1-minute timer stops counting. When the host sends a control packet with MTC bit set, the 1-minute timer restarts from 0. This allows accurate setting of a time-of-day function. 8.4.9 ROAMING CONTROL PACKET (ID = 05H) The roaming control packet controls the features of the PCD5013 that allow implementation of a roaming pager. IRS: ignore re-synchronization signal (Table 13). When this bit is set, the PCD5013 does not go asynchronous when detecting an Ar or Ar signal during searches for A-words. It merely reports that the re-synchronization signal was received by setting RSR to 1 in the Roaming Status packet. This allows the host to decide what to do when the paging device is synchronous to more than one channel and only one channel is sending the re-synchronization signal. It also prevents the PCD5013 from losing synchronization when it detects the re-synchronization signal while the paging device is checking an unknown channel. This bit is set and cleared by the host. Value after reset = 0. NBC: network bit check (Table 13). Setting this bit enables reporting of the received network bit value (NBU and n) in the Roaming Status Packet. Setting this bit also makes the PCD5013 abandon a frame after the Frame Info word without synchronizing to the frame if the frame information word is uncorrectable or if the n bit in the frame information word is not set. If the PCD5013 is in synchronous mode when this occurs (probably due to synchronizing to a second channel), it maintains synchronization to the original channel. Table 13 Roaming Control Packet bit assignments BYTE 3 2 1 0 BIT 7 0 IRS RND 0 BIT 6 0 NBC ABI 0 BIT 5 0 MCM SAS MFC1 BIT 4 0 IS1 DAS MFC0 BIT 3 0 SDF AF11 0 BIT 2 1 RSP AF10 0 BIT 1 0 SND AF9 MCO1 BIT 0 1 CND AF8 MCO0 1999 Apr 12 22 Philips Semiconductors Product specification FLEXTM roaming decoder II SND: start noise detect (Table 13). Setting this bit while the PCD5013 is battery saving causes it to warm-up the receiver, run a noise detect, and report the result of the noise detect via NDR in the Roaming Status Packet. This bit is set by the host, and cleared by the PCD5013 once it has been processed. If the time comes for the PCD5013 to warm-up automatically or the SAS bit is set while an SND is being processed, the noise detect is abandoned and the abandoned noise detect result (NDR = 01) is sent in the Roaming Status Packet. Value after reset = 0. CND: continuous noise detect (Table 13). Setting this bit causes the PCD5013 to do continuous noise detects during the decoded block data of a frame. The results of the noise detect is only reported if noise is detected (NDR = 11). Only one noise detected result (NDR = 11) is sent per block. If the PCD5013 has not completed a noise detect when it shuts down for the frame, that noise detect is abandoned, but no abandon result (NDR = 01) is sent. This bit is set and cleared by the host. Value after reset = 0. RND: report noise detects (Table 13). Setting this bit causes the PCD5013 to report the results of the noise detects it does under normal asynchronous operation (when first turned on and when asynchronous). The results of the noise detect is reported via NDR in the Roaming Status Packet. This bit is set and cleared by the host. Value after reset = 0. ABI: all block information words (Table 13). When this bit is set, the PCD5013 sends all received Block Information words 2-4 to the host. Note: Setting the SBI bit in the Control Packet only enables errored and real-time clock related block info words. Value after reset = 0. SAS: start A-word search (Table 13). Setting this bit while in asynchronous battery save mode causes the PCD5013 to warm-up the receiver and run an A-word search. If, during the A-word search, the PCD5013 finds sufficient FLEXTM signal, it enters synchronous mode and start decoding the frame. If the A-word search times-out without finding sufficient FLEXTM signal, it enters a battery save mode and continue doing periodic noise detects. PCD5013 The time-out for the A-word searches is controlled by the AST bits in the Timing Control Packet and the MOT bit in the Configuration Packet. The A-word search takes priority over noise detects. Therefore, if the PCD5013 is performing an A-word search and the time comes to do automatic noise detect, the noise detect is not performed. This bit is set by the host, and cleared by the PCD5013 once it has been acted on. Value after reset = 0. MFC: missed frame control (Tables 14 and 13). These bits control the frames for which missing frame data (MS1, MFI, MS2, MBI, and MAW) is reported in the Roaming Status Packet. Value after reset = 0. Table 14 Missed Frame Control (MFC bits) MFC1 0 0 1 1 MFC0 0 1 0 1 MISSING FRAME DATA REPORTED never only during frames 0 through 3 only during frames 0 through 7 always MCO: maximum carry on (Table 13). The value of these bits sets the maximum carry on that the PCD5013 follows. For example, if the PCD5013 receives a carry on of 3 over the air and MCO is set to 1, the PCD5013 only carries on for one frame. Value after reset = 3. DAS: disable A-word search (Table 13). When this bit is set, an A-word search does not automatically occur after a noise detect in asynchronous mode finds FLEXTM signal. This includes automatic noise detects and noise detects initiated by the host by setting SND. The PCD5013 shuts down the receiver after the noise detect completes regardless of the result. When this bit is cleared, A-word searches occur after a noise detect finds signal in asynchronous mode. Value after reset = 0. 1999 Apr 12 23 Philips Semiconductors Product specification FLEXTM roaming decoder II 8.4.10 TIMING CONTROL PACKET (ID = 06H) - LBU bit in the status packet is set - EA bit in the status packet is set - BOE bit in the status packet is set. PCD5013 The timing control packet gives the host control of the timing used when the PCD5013 is in asynchronous mode. The packet ID for the timing control packet is 6. AST: A-word search time (Table 15). The value of these bits sets the A-word search time for all asynchronous A-word searches in units of 80 ms (e.g. value of 1 is 80 ms, a value of 2 is 160 ms, etc.). If the value is 0, the PCD5013 defaults to the 1-minute (MOT = 1) or 4-minute (MOT = 0) A-word search time controlled by the MOT bit in the configuration packet. Value after reset = 0. ABT: asynchronous battery-save time (Table 15). The value of these bits sets the battery save time (time from the beginning of one automatic noise detect to the beginning of the next automatic noise detect) in asynchronous mode in units of 80 ms (e.g. value of 1 is 80 ms, a value of 2 is 160 ms, etc.) If the value is 0, the battery save time is set to the default value of 1.5 seconds. The minimum allowed ABT is 320 ms, therefore values of 1, 2, 3, and 4 are invalid. Value after reset = 0. 8.4.11 STATUS PACKET (ID = 7FH) FIV: frame information valid (Table 16). This bit is set, when a valid frame information word has been received since becoming synchronous to the system and the f and c fields contain valid values. If this bit is clear, no valid frame information words have been received since the PCD5013 became synchronous to the system. This value changes from 0 to 1 at the end of block 0 (Fig.18) of the frame in which the first frame information word was properly received. It is cleared when the PCD5013 goes into asynchronous mode (see SM bit below). This bit is initialized to 0 when the PCD5013 is reset and when the PCD5013 is turned off by clearing the ON bit in the control packet. f: current frame number (Table 16). This value is updated every frame regardless of whether the PCD5013 needs to decode the frame. This value changes to its proper value for a frame at the end of block 0 of the frame. The value of these bits is not guaranteed when FIV is 0. c: current system cycle number (Table 16). This value is updated every frame regardless of whether the PCD5013 needs to decode the frame. This value changes to its proper value for a frame at the end of block 0 of the frame. The value of these bits is not guaranteed when FIV is 0. SM: synchronous mode (Table 16). This bit is set, when the PCD5013 is synchronous to the system. The PCD5013 sets this bit when the first synchronization words are received. It clears this bit when the PCD5013 has not properly received both synchronization words in any frame for 8, 16, or 32 minutes (depending on the number of assigned frames and the system collapse). This bit is initialized to 0 when the PCD5013 is reset and when it is turned off by clearing the ON bit in the control packet. The status packet contains various types of information that the host may require and is sent to the host: * Whenever the PCD5013 is polled and has no other data to send * On events for which the PCD5013 is configured to send the status packet (Sections 8.4.4 and 8.4.7). In this case, the PCD5013 prompts the host to read a status packet for the following conditions: - SMU bit in the status packet and the SME bit in the configuration packet are set - MT bit in the status packet and the MTE bit in the configuration packet are set - EOF bit in the status packet is set Table 15 Timing Control Packet bit assignments BYTE 3 2 1 0 BIT 7 0 0 AST7 ABT7 BIT 6 0 0 AST6 ABT6 BIT 5 1 0 AST5 ABT5 BIT 4 0 0 AST4 ABT4 BIT 3 0 0 AST3 ABT3 BIT 2 f2 0 AST2 ABT2 BIT 1 f1 0 AST1 ABT1 BIT 0 f0 0 AST0 ABT0 1999 Apr 12 24 Philips Semiconductors Product specification FLEXTM roaming decoder II SMU: synchronous mode update (Table 16). This bit is set if the SM bit has been updated in this packet. After the PCD5013 has been turned on, this bit is set when the first synchronization words are found (SM changes to 1) or when the first synchronization search period (meaning the receiver is active during this time) expires (SM stays 0), after the PCD5013 is turned on. The latter condition gives the host the option of assuming the paging device is in range when it is turned on, and displaying out-of-range only after the initial search period expires. After the initial synchronous mode update, the SMU bit is set whenever the PCD5013 switches from/to synchronous mode. The bit is cleared when read. Changes in the SM bit due to turning off the PCD5013 does not set the SMU bit. This bit is initialized to 0 when the PCD5013 is reset. LB: low battery (Table 16). Set to the value last read from the LOBAT pin. The host controls when the LOBAT pin is read via the receiver control packets. This bit is initialized to 0 at reset. It is also initialized to the inverse of the LBP bit in the configuration packet, when the PCD5013 is turned on, by setting the ON bit in the control packet. LBU: low battery update (Table 16). This bit is set if the value on two consecutive reads of the LOBAT pin yielded different results. The bit is cleared when read. The host controls when the LOBAT pin is read via the receiver control packets. Changes in the LB bit due to turning on the PCD5013 do not cause the LBU bit to be set. This bit is initialized to 0 when the PCD5013 is reset. EOF: end of frame (Table 16). Set when the PCD5013 is in all frame mode (AFM) (Section 8.8.4), and the end of the frame has been reached. The PCD5013 is in the AFM if the AFM enable counter is non-zero, if any temporary address enabled (TAE) counter is non-zero (Section 8.8.4) or if the FAF bit in the AFM packet is set. The bit is cleared when read and initialized to 0 when the PCD5013 is reset. MT: minute time-out (Table 16). Set if one minute has elapsed. The bit is cleared when read. This bit is initialized to 0 when the PCD5013 is reset. BOE: buffer overflow error (Table 16). Set when information has been lost owing to slow host response time. When the PCD5013 detects that its SPI transmit buffer has overflowed, it clears the transmit buffer, turns off decoding by clearing the ON bit in the control packet, and sets this bit. The bit is cleared when read. This bit is initialized to 0 when the PCD5013 is reset. PCD5013 EA: end of addresses (Table 16). If EAE of the control packet is set and an address is detected in a frame, EA is set after the PCD5013 processes the last address in the frame. Since data packets take priority over the status packet, the status packet with the EA bit set is guaranteed to come after all address packets for the frame. Cleared when read. This bit is initialized to 0 when the PCD5013 is reset. x: unused bits (Table 16). The value of these bits is not guaranteed. 8.4.12 RECEIVER SHUTDOWN PACKET (ID = 7EH) The Receiver Shutdown Packet is sent in both synchronous and asynchronous mode. It is designed to indicate to the host that the receiver is turned off and how much time there is until the PCD5013 automatically turns it back on. This enables the host to perform other tasks such as monitoring other pager channels. FNV: frame number valid (Table 17). This bit is set if the last decoded frame information word was correctable and the frame number was the expected value. When in asynchronous mode, this value is 0. CF: current frame (Table 17). When in synchronous mode, this is the current frame number. This value is latched on the negative edge of the READY line when this packet is sent to the host. The value of this field is valid only if the PCD5013 is in synchronous mode and the FIV bit in the status packet is set. When in asynchronous mode, this value is 0. TNF: time to next frame (Table 17). When in synchronous mode TNF indicates the time to the start of the A-word check if the PCD5013 were to warm-up for the next frame. When in asynchronous mode TNF indicates the time to the start of the next automatic noise detect. See section 8.8.9 for an explanation on how to use this value. This value is latched on the negative edge of the READY line when this packet is sent to the host. FCO: frame carried on (Table 17). Set if the PCD5013 is decoding the next frame due to the reception of a non-zero carry-on value in the current or a previous frame. When in asynchronous mode, this value is 0. NAF: next assigned frame (Table 17). This is the frame number of the next frame the PCD5013 was scheduled to decode when the receiver shut down. The value of this field is valid only if the PCD5013 is in synchronous mode and the FIV bit in the status packet is set. When in asynchronous mode this value is 0. 1999 Apr 12 25 Philips Semiconductors Product specification FLEXTM roaming decoder II Table 16 Status packet bit assignments BYTE 3 2 1 0 BIT 7 0 FIV SM SMU BIT 6 1 f6 LB LBU BIT 5 1 f5 x x BIT 4 1 f4 x MT BIT 3 1 f3 c3 x BIT 2 1 f2 c2 EOF PCD5013 BIT 1 1 f1 c1 EA BIT 0 1 f0 c0 BOE Table 17 Receiver Shutdown Packet bit assignments BYTE 3 2 1 0 BIT 7 0 FNV TNF7 FCO BIT 6 1 CF6 TNF6 NAF6 BIT 5 1 CF5 TNF5 NAF5 BIT 4 1 CF4 TNF4 NAF4 BIT 3 1 CF3 TNF3 NAF3 BIT 2 1 CF2 TNF2 NAF2 BIT 1 1 CF1 TNF1 NAF1 BIT 0 0 CF0 TNF0 NAF0 1999 Apr 12 26 Philips Semiconductors Product specification FLEXTM roaming decoder II 8.4.13 ROAMING STATUS PACKET (ID = 60H) PCD5013 NBU: network bit update (Table 19). Set when the NBC bit in the roaming control packet is set and a frame information word is received with a correctable number of errors. This bit is not set when the frame information word is not received due to missing the first synchronization pattern (A/A). This bit is cleared when read. n: network bit value (Table 19). When NBU is set, this is the value of the n bit in the last received frame information word. NDR: noise detect result (Tables 18 and 19). These bits indicate the result of a noise detect. The results of noise detects initiated by setting the SND bit in the roaming control packet is always reported. The results of the automatic noise detects performed in asynchronous mode is only reported if the RND bit is set in the roaming control packet. When continuous noise detects during block data are enabled by setting the CND bit in the roaming control packet, only the `No FLEXTM signal detected' result is reported. These bits are cleared when read. Table 18 Noise Detect Result (NDR bits) NDR1 0 0 1 1 NDR0 0 1 0 1 NOISE DETECT RESULT No Information Noise Detect was abandoned FLEXTM signal detected FLEXTM signal not detected The PCD5013 automatically prompts the host to read a Roaming Status Packet if RSR, MS1, MFI, MS2, MBI, MAW, NBU, NDR 1, NDR 0, or SCU is set. RSR: re-synchronization signal received (Table 19). Set when the PCD5013 detected a re-synchronization signal (Ar/Ar) and the host configured the PCD5013 to ignore it via the IRS bit in the roaming control packet. This bit is cleared when read. MS1: missed synchronization 1 (Table 19). Set when the PCD5013 fails to detect the first synchronization pattern (A/A) of a FLEXTM frame and the PCD5013 was configured to report missed frame information via the MFC bit in the roaming control packet. This bit is cleared when read. MFI: missed frame information word (Table 19). Set when the frame information word is received with an uncorrectable number of errors and the PCD5013 was configured to report missed frame information via the MFC bit in the roaming control packet. This bit is cleared when read. MS2: missed synchronization 2 (Table 19). Set when the PCD5013 failed to detect the second synchronization pattern (C/C) of a frame and PCD5013 was configured to report missed frame information via the MFC bit in the roaming control packet. This bit is cleared when read. MBI: missed block information word 1 (Table 19). Set when at least one of the block information word ones is received with an uncorrectable number of errors and PCD5013 was configured to report missed frame information via the MFC bit in the roaming control packet. This bit is set no more than once per frame regardless of the number of missed block information word 1's in the frame. This bit is cleared when read. MAW: missed address word (Table 19). Set when any address words in the address field is received with an uncorrectable number of errors and PCD5013 was configured to report missed frame information via the MFC bit in the roaming control packet. This bit is set no more than once per frame regardless of the number of missed address words in the frame. This bit is cleared when read. Table 19 Roaming Status packet bit assignments BYTE 3 2 1 0 1999 Apr 12 BIT 7 0 RSR x x BIT 6 1 MS1 x x BIT 5 1 MFI x x SCU: system collapse update (Table 19). Set when the PCD5013 is configured for manual collapse mode by setting the MCM bit in the roaming control packet and the system collapse of a frame is received. This bit is set no more than once per frame regardless of the number of phases in the frame. This bit is not set in frames in which no block information word 1's is received properly. This bit is cleared when read. RSC: received system collapse (Table 19). When SCU is set, this value represents the system collapse value that was received in the frame. BIT 4 0 MS2 x x 27 BIT 3 0 MBI x SCU BIT 2 0 MAW x RSC2 BIT 1 1 NBU NDR1 RSC1 BIT 0 0 n NDR0 RSC0 Philips Semiconductors Product specification FLEXTM roaming decoder II 8.5 8.5.1 Receiver control interface GENERAL PCD5013 This allows the designer to force the receiver control lines to the receiver off setting with external pull-up or pull-down resistors before the host can configure these settings in the PCD5013. 8.5.4 RECEIVER OFF STATE (ID = 10H) The PCD5013 has 8 programmable receiver control lines, S0 to S7. The host can program via SPI packets what setting is applied to the receiver control lines, the duration of warm-up and shut-down stages and the polling of the LOBAT pin. This programmability allows the PCD5013 to interface with many off-the-shelf receiver ICs. Note that these packets are ignored when sent while decoding is enabled (ON bit is set in the control packet). 8.5.2 LOW BATTERY DETECTION The receiver off state is configured by the receiver off setting packet (Table 20), which defines the settings to be applied when the PCD5013 decides to switch the receiver off. LBC: low battery check (Table 20). If this bit is set, the PCD5013 checks the status of the LOBAT port just before leaving the receiver off state. Value after reset = 0. CLS: control line setting (Table 20). This is the value to be output on the receiver control lines for the receiver off state. Value after reset = 0. ST: step time (Table 20). This sets the duration of the warm-up off time. The setting is in steps of 625 s. Valid values are 625 s (ST = 01H) to 159.375 ms (ST = FFH). Value after reset = 01H. The PCD5013 can be configured to poll the LOBAT pin at the end of every receiver control setting. This check can be enabled or disabled for each receiver control setting. If the poll is enabled for a setting, the pin is read just before the PCD5013 activates the next setting on the receiver control lines. The PCD5013 sends a status packet whenever the value differs from the previous time that the LOBAT pin was polled. 8.5.3 RECEIVER SETTINGS AT RESET The receiver control ports are 3-state outputs which are set to high impedance when the PCD5013 is reset, until the corresponding FRS bit in the receiver line control packet is set or the PCD5013 is turned on for the first time after a reset (by setting the ON bit in the control packet). Table 20 Receiver off setting packet bit assignments BYTE 3 2 1 0 BIT 7 0 0 CLS7 ST7 BIT 6 0 0 CLS6 ST6 BIT 5 0 0 CLS5 ST5 BIT 4 1 0 CLS4 ST4 BIT 3 0 LBC CLS3 ST3 BIT 2 0 0 CLS2 ST2 BIT 1 0 0 CLS1 ST1 BIT 0 0 0 CLS0 ST0 1999 Apr 12 28 Philips Semiconductors Product specification FLEXTM roaming decoder II 8.5.5 RECEIVER WARM-UP SEQUENCES PCD5013 160 ms, the receiver remains in the 1600 sps sync setting or the 3200 sps sync setting from the end of the last used warm-up setting until valid signals are expected (160 ms after the start of the warm-up off time). Figure 12 shows the receiver warm-up sequence while decoding, when all warm-up settings are enabled. 8.5.5.1 Normal receiver warm-up sequence The PCD5013 allows for up to 6 steps associated with warming-up the receiver. When the PCD5013 turns on the receiver while decoding, it starts the warm-up sequence 160 ms before it requires valid signals at the EXTS1 and EXTS0 input pins. 1. The PCD5013 leaves the receiver control lines in the off state for the programmed warm-up off time. 2. The first warm-up setting, if enabled, is applied to the receiver control lines for the amount of time programmed for that setting. 3. Subsequent warm-up settings are applied to the receiver control lines for their corresponding time until a disabled warm-up setting is found. 4. At the end of the last used warm-up setting, the 1600 symbols per second (sps) sync setting or the 3200 sps sync setting is applied to the receiver control lines depending on the PCD5013 current state. The PCD5013 must be configured such that the sum of all of the used warm-up times and the warm-up off time does not exceed 160 ms. If it exceeds 160 ms, the PCD5013 executes the receiver shut-down sequence 160 ms after the start of the warm-up off time. If the sum of all of the used warm-up times and the warm-up off times is less than 8.5.5.2 Host initiated receiver warm-up sequence A host can initiate a receiver warm-up sequence is by one of the following actions: * Turning on the PCD5013 by setting the ON bit in the control packet * Requesting a noise detect by setting the SND bit in the roaming control packet * Requesting an A-word search by setting the SAS bit in the roaming control packet. A host initiated receiver warm-up sequence (see Fig.13) differs from the sequence described in Section 8.5.5.1. No receiver warm-up off time is applied, instead the PCD5013 immediately begins to apply the receiver warm-up settings. Once a disabled warm-up setting is found, the "3200 sps sync setting" (for ON and SND warm-ups) or the "1600 sps sync setting" (for SAS warm-ups) is applied to the receiver control lines. The decoder then expects valid signals after the 3200 sps sync warm-up time. handbook, full pagewidth 160 ms warm-up off time warm-up time 1 warm-up setting 1 warm-up time 2 warm-up setting 2 warm-up time 3 warm-up setting 3 warm-up time 4 warm-up setting 4 warm-up time 5 warm-up setting 5 1600 sps or 3200 sps sync setting receiver control line setting off possible LOBAT check possible LOBAT check possible LOBAT check possible LOBAT check possible LOBAT check possible LOBAT check EXTS1 & EXTS0 signals are expected to be valid here MGK265 Fig.12 Receiver warm-up sequence while decoding. handbook, full pagewidth warm-up time 1 off warm-up setting 1 warm-up time 2 warm-up setting 2 warm-up time 3 warm-up setting 3 warm-up time 4 warm-up setting 4 warm-up time 5 warm-up setting 5 3200 sps sync warm-up time 3200 sps sync setting receiver control line setting possible LOBAT check possible LOBAT check possible LOBAT check possible LOBAT check possible LOBAT check possible LOBAT check EXTS1 & EXTS0 signals are expected to be valid here MGK266 Fig.13 First receiver warm-up sequence after turning decoding on. 1999 Apr 12 29 Philips Semiconductors Product specification FLEXTM roaming decoder II 8.5.5.3 Receiver warm-up setting packets (ID = 11H to 15H) PCD5013 ST: step time (Table 22). This sets the duration time for receiver warm-up until the next receiver state. The setting is in 625 s steps and valid values are: 625 s (ST = 01H) to 79.375 ms (ST = 7FH). Value after reset = 01H. s: setting number, see Tables 21 and 22 for the s names and values and location in the receiver warm-up packet. CLS: control line setting (Table 22). This is the value to be output on the receiver control lines (S0 to S7) for this receiver warm-up state. Value after reset = 0. SE: step enable (Table 22). The receiver setting is enabled when the bit is set. If the bit is cleared then that step in the receiver warm-up sequence is disabled and all following steps are ignored. Value after reset = 0. LBC: low battery check (Table 22). If this bit is set, the PCD5013 checks the status of the LOBAT port just before leaving this receiver warm-up state. Value after reset = 0. Table 21 Receiver warm-up setting numbers s3 0 0 0 0 0 s2 0 0 0 1 1 s1 0 1 1 0 0 s0 1 0 1 0 1 SETTING NAME warm-up 1 warm-up 2 warm-up 3 warm-up 4 warm-up 5 Table 22 Receiver warm-up setting packet bit assignments BYTE 3 2 1 0 BIT 7 0 SE CLS7 0 BIT 6 0 0 CLS6 ST6 BIT 5 0 0 CLS5 ST5 BIT 4 1 0 CLS4 ST4 BIT 3 s3 LBC CLS3 ST3 BIT 2 s2 0 CLS2 ST2 BIT 1 s1 0 CLS1 ST1 BIT 0 s0 0 CLS0 ST0 1999 Apr 12 30 Philips Semiconductors Product specification FLEXTM roaming decoder II 8.5.6 ACTIVE RECEIVER STATES PCD5013 8.5.6.1 General In addition to the warm-up and shut-down states, the PCD5013 has four active receiver states. When these settings are applied to the receiver control lines, the PCD5013 is decoding the EXTS1 and EXTS0 input signals. The timing of these signals and their duration depends on the FLEXTM data stream. Because of this, there is no time setting associated with these settings (with the exception of the 3200 sps sync setting). The four settings are as follows: 1600 sps sync setting: applied when the PCD5013 searches for a 1600 sps signal. 3200 sps sync setting: applied when the PCD5013 searches for a 3200 sps signal. 1600 sps data setting: applied after the PCD5013 has found the C or C sync word in the sync 2 section of a 1600 sps frame. 3200 sps data setting: applied after the PCD5013 has found the C or C sync word in the sync 2 section of a 3200 sps frame. Figure 14 shows some examples of how these settings are used in the PCD5013. handbook, full pagewidth FLEXTM signal block 10 sync 1 frame info sync 2 block 0 receiver control line setting example #1 1600 sps data or 3200 sps data or last used warm up setting 1600 sps sync setting 3200 sps sync setting 3200 sps data setting receiver control line setting example #2 possible LOBAT check 1600 sps data or 3200 sps data or last used warm up setting possible LOBAT check 1600 sps sync setting possible LOBAT check 1600 sps data setting MGK268 possible LOBAT check possible LOBAT check Fig.14 Examples of receiver control transitions. 1999 Apr 12 31 Philips Semiconductors Product specification FLEXTM roaming decoder II 8.5.6.2 Receiver on setting packets (ID = 16H to 19H) Table 23 s names and values s3 0 1 1 8.5.7 s2 1 0 0 s1 1 0 0 s0 1 0 1 PCD5013 LBC: low battery check (Tables 24 and 25). If this bit is set, the PCD5013 checks the status of the LOBAT port just before leaving this receiver sync setting state. Value after reset = 0. CLS: control line setting (Tables 24 and 25). This is the value to be output on the receiver control lines for this receiver sync setting state. Value after reset = 0. ST: step time (Table 24). This sets the waiting time, before expecting good signals at EXTS1 and EXTS0 at the end of the warm-up sequence, after turning decoding on. The setting is in steps of 625 s. Valid values are: 625 s (ST = 01H) to 79.375 ms (ST = 7FH). Value after reset = 01H. s: setting number, see Tables 23 and 25 for the s names and values and location in the receiver on setting packet. SETTING NAME 1600 sps sync 3200 sps data 1600 sps data FORCING RECEIVER LINES (ID = 0FH) This packet (Table 26) enables host control over the receiver control line (S0 to S7) settings in all modes except reset. In reset, the receiver control lines are high impedance. FRS: force receiver setting (Table 26). Setting a bit causes the associated CLS bit in this packet to override the internal receiver control settings on the corresponding receiver control line. Clearing a bit returns control of the corresponding receiver control line to the PCD5013. Value after reset = 0. CLS: control line setting (Table 26). This bit setting is applied to the corresponding receiver control line if the associated FRS bit is set in this packet. Value after reset = 0. Table 24 3200 sps sync setting packet bit assignments BYTE 3 2 1 0 BIT 7 0 0 CLS7 0 BIT 6 0 0 CLS6 ST6 BIT 5 0 0 CLS5 ST5 BIT 4 1 0 CLS4 ST4 BIT 3 0 LBC CLS3 ST3 BIT 2 1 0 CLS2 ST2 BIT 1 1 0 CLS1 ST1 BIT 0 0 0 CLS0 ST0 Table 25 Receiver on setting packet bit assignments BYTE 3 2 1 0 BIT 7 0 0 CLS7 0 BIT 6 0 0 CLS6 0 BIT 5 0 0 CLS5 0 BIT 4 1 0 CLS4 0 BIT 3 s3 LBC CLS3 0 BIT 2 s2 0 CLS2 0 BIT 1 s1 0 CLS1 0 BIT 0 s0 0 CLS0 0 Table 26 Receiver line control packet bit assignments BYTE 3 2 1 0 BIT 7 0 0 FRS7 CLS7 BIT 6 0 0 FRS6 CLS6 BIT 5 0 0 FRS5 CLS5 BIT 4 0 0 FRS4 CLS4 BIT 3 1 0 FRS3 CLS3 BIT 2 1 0 FRS2 CLS2 BIT 1 1 0 FRS1 CLS1 BIT 0 1 0 FRS0 CLS0 1999 Apr 12 32 Philips Semiconductors Product specification FLEXTM roaming decoder II 8.5.8 RECEIVER SHUT-DOWN SEQUENCE PCD5013 LBC: low battery check (Table 28). If this bit is set, the PCD5013 checks the status of the LOBAT port just before leaving this receiver shut-down state. Value after reset = 0. CLS: control line setting (Table 28). This is the value to be output on the receiver control lines (S0 to S7) for this receiver shut-down state. Value after reset = 0. ST: step time (Table 28). This sets the duration time for receiver shut-down, until the next receiver state. The setting is in steps of 625 s. Valid values are 625 s (ST = 01H) to 39.375 ms (ST = 3FH). Value after reset = 01H. s: setting number, see Tables 27 and 28 for the s names and values and location in the receiver shut-down packet. Table 27 s names and values s 0 1 SETTING NAME shut-down 1 shut-down 2 The PCD5013 allows up to 3 steps associated with shutting down the receiver. When the PCD5013 decides to turn off the receiver, the first shut-down setting, if enabled, is applied to the receiver control lines for the corresponding shut-down time. At the end of the last used shut-down time, the receiver off setting is applied to the receiver control lines. If the first shut-down setting is not enabled, the PCD5013 switches directly from the receiver on to the receiver off setting. Figure 15 shows the receiver shut-down sequence when all shut-down settings are enabled. If the receiver is on or being warmed up when the decoder is turned off (by clearing the ON bit in the control packet), the PCD5013 immediately executes the receiver shut-down sequence. If the PCD5013 is executing the shut-down sequence when turned on (with the ON bit in the control packet set) the PCD5013 completes the shut-down sequence before starting the warm-up sequence. 8.5.8.1 Receiver shut-down setting packets (ID = 1AH to 1BH) SE: step enable (Table 28). The receiver setting is enabled when the bit is set. If the bit is cleared then that step in the receiver shut-down sequence is disabled and all following steps are ignored. Value after reset = 0. Table 28 Receiver shut-down stages BYTE 3 2 1 0 BIT 7 0 SE CLS7 0 BIT 6 0 0 CLS6 0 BIT 5 0 0 CLS5 ST5 BIT 4 1 0 CLS4 ST4 BIT 3 1 LBC CLS3 ST3 BIT 2 0 0 CLS2 ST2 BIT 1 1 0 CLS1 ST1 BIT 0 s 0 CLS0 ST0 handbook, full pagewidth shut down time 1 1600 sps or 3200 sps sync or data setting shut down setting 1 shut down time 2 shut down setting 2 off MGK267 receiver control line setting possible LOBAT check possible LOBAT check possible LOBAT check Fig.15 Receiver shut-down sequence. 1999 Apr 12 33 Philips Semiconductors Product specification FLEXTM roaming decoder II 8.6 8.6.1 Configuration of the FLEXTM CAPCODE GENERAL PCD5013 When the FLEXTM standard pager collapse value of 4 (battery cycle of 16 frames) is used, the pager collapse field can be omitted. The collapse value is a number between 0 and 7 and defines how often the decoding device looks for messages on the FLEXTM channel. For a given collapse value b, the decoding device looks in every 2b frames. Thus an address with an assigned base frame of 3 and a collapse value of 5 typically looks for messages in frame 3 and every 32 frames thereafter (i.e. frames 3, 35, 67 and 99). A CAPCODE specifies a decoder address, the collapse value of the address and whether single-phase, any-phase or all-phase address. The PCD5013 supports single-phase and any-phase operation. The FLEXTM protocol provides a standard mechanism to derive phase and frame in which an address should be transmitted. If this mechanism is not used, a CAPCODE also specifies the phase and frame assigned to the address. 8.6.2 CAPCODE FORMAT The FLEXTM CAPCODE consist of a series of decimal and alphabetic fields, see Fig.16 for the field definitions. Frame field, optional 3 digit decimal handbook, full pagewidth field, represents the frame number if standard frame and phase embedding rules are not used. CAPCODE type, mandatory alphabetic character, indicates rules for deriving phase and frame from address field. P1225U2234550121 Roaming capability, optional alphabetic character 'P' indicates no roaming capabilities. Pager collapse (battery cycle), optional 1 digit decimal field (mandatory if frame number field is included) indicates pager collapse value. Address field, mandatory 7, 9 or 10 digit decimal field, contains the information from which the BCH address codewords for this CAPCODE are derived. MBK096 Fig.16 CAPCODE format. 1999 Apr 12 34 Philips Semiconductors Product specification FLEXTM roaming decoder II 8.6.3 CAPCODE RANGES PCD5013 A long CAPCODE represents addresses situated above 2101248 subdivided into categories (uncoordinated, global, country) to allow different allocation schemes to coexist. Table 29 defines the address usage assignment. All addresses not listed in this table are not defined and reserved for future use. A CAPCODE represents user addresses ranging from 1 to 5370810366. A short CAPCODE can have address values below 2031615 and are represented in the data stream by a single address codeword. Some short addresses have been reserved for special purposes: information service addresses, network addresses, temporary (group) addresses and operator messaging addresses. Table 29 CAPCODE assignment table CAPCODE ADDRESS VALUE DESCRIPTION from 0000000000 0000000001 0001933313 0001998849 0002009088 0002025472 0002029568 0002029584 0002029600 0002031615 0002101249 0102101251 0402101251 1075843073 2149584897 3223326721 3923326751 4280000001 4285000001 4290000001 4291000001 Notes 1. Country: the addresses are coordinated within each country and with countries along borders. 2. Global: address is coordinated to be unique world-wide. 3. Information service: currently, the rules governing the use of these addresses are not defined. 4. World-wide: 1000 addresses are assigned to each country for world-wide use. 0001933312 0001998848 0002009087 0002025471 0002029567 0002029583 0002029599 0002031614 0002101248 0102101250 0402101250 1075843072 2149584896 3223326720 3923326750 4280000000 4285000000 4290000000 4291000000 4297068542 to illegal short addresses illegal reserved for future use Information service addresses network addresses temporary addresses operator messaging addresses reserved for future use invalid, not used long address set 1-2 uncoordinated long address set 1-2 country; note 1 long address set 1-2 global; note 2 long address set 1-3 global; note 2 long address set 1-4 global; note 2 long address set 2-3 country; note 1 long address set 2-3 reserved long address set 2-3 information service, global; notes 2 and 3 long address set 2-3 information service, country; notes 1 and 3 long address set 2-3 information service, world-wide; notes 3 and 4 reserved for future use 1999 Apr 12 35 Philips Semiconductors Product specification FLEXTM roaming decoder II 8.6.4 ADDRESS CALCULATION PCD5013 Table 30 Address word range definitions TYPE Idle word (illegal address) Long address 1 Short address Long address 3 Long address 4 Short address (reserved) Information service address Network address Temporary address Short address (reserved) Long address 2 Idle word (illegal address) HEX VALUE 000000 000001 to 008000 008001 to 1E0000 1E0001 to 1E8000 1E8001 to 1F0000 1F0001 to 1F27FF 1F2800 to 1F67FF 1F6800 to 1F77FF 1F7800 to 1F780F 1F7820 to 1F7FFE 1F7FFF to 1FFFFE 1FFFFF Address codeword values generally do not coincide with (part of) the user address as specified in the CAPCODE. To find the address codewords corresponding to a user address a conversion has to be done (Table 31). The type of conversion depends on the CAPCODE range in which the user address is located. Note that addresses are transmitted LSB first (differently to POCSAG). Short addresses, are transmitted in a single address codeword where as long addresses are transmitted in two consecutive address codewords. The first codeword of a long address contains the lower part of the address, the second codeword the upper part. By combining two long address codewords from different banks 6 long address ranges are created: 1 to 2, 1 to 3, 1 to 4, 2 to 3, 2 to 4 and 3 to 4. Ranges 2 to 4 and 3 to 4 are as yet undefined and reserved. Table 31 describes how to calculate the 21-bit address codeword which is transmitted over the air. Table 31 Address word calculation TYPE Short address Long address, range 1 to 2; note 6 Long address, ranges 1 to 3 and 1 to 4 Long address, range 2 to 3 Notes 1. All numbers are in hexadecimal format. Operator messaging address 1F7810 to 1F781F LOWER ADDRESS CODEWORD; notes 1, 2 and 3 CAPCODE + 8000 1 + ((CAPCODE - 1F9001) MOD 8000) 1 + ((CAPCODE - 1F9001) MOD 8000) UPPER ADDRESS CODEWORD; notes 1, 3 and 4 note 5 1FFFFF - ((CAPCODE - 1F9001) DIV 8000) 1D8000 + ((CAPCODE - 1F9001) DIV 8000) 1F7FFF + ((CAPCODE - 1F8FFF) MOD 8000) 1C8000 + ((CAPCODE - 1F8FFF) DIV 8000) 2. The MOD operator gives the remainder of an integer division. 3. CAPCODE refers to the value of the address field in a FLEXTM CAPCODE. 4. The DIV operator is the integer division. 5. A short address consists of a single codeword. 6. The upper codeword range in bank 2 is used from the highest address downwards, i.e. the lowest value of the CAPCODE produces a codeword value of 1FFFFEH. 1999 Apr 12 36 Philips Semiconductors Product specification FLEXTM roaming decoder II 8.6.5 PHASE AND FRAME CALCULATION PCD5013 Phase number = ((Address - Offset) DIV 4) MOD 4 Frame = ((Address - Offset) DIV 16) MOD 128 where DIV is the integer division and MOD is the remainder of an integer division. For a CAPCODE not using the standard rules for extracting phase and base frame (types U to Z) the 3-digit frame field 000 to 127 and a single digit decimal pager collapse 0 to 5 can precede the CAPCODE type. When these fields are not included, the paging device or the subscriber database must be accessed to determine the assigned frame and collapse value. The CAPCODE for a roaming pager uses an Alpha character to describe the level of roaming capability. The Alpha characters descriptions are shown in Table 33. The method for specifying phase and base frame of a pager is specified in the CAPCODE type. * The phase and base frame are extracted by standard rules from the user address field in the CAPCODE (CAPCODE types A to L) * The phase is indicated by the CAPCODE type (Table 32) and the base frame is specified in the frame field of the CAPCODE (CAPCODE types U to Z). For easy allocation of (up to 4) consecutive CAPCODEs having the same phase and frame, an offset in the range 0 to 3 is subtracted from the user address for the purposes of phase and frame extraction. The offset is determined by the CAPCODE type. The standard rules for extracting phase and base frame from the user address are (phase numbers 0 to 3 correspond to phases A to D): Table 32 Frame and phase extraction for different CAPCODE types CAPCODE TYPE A B C D E F G H I J K L U V W X Y Z Note 1. All-phase decoding is not defined in FLEXTM G1.8 and, therefore, is not supported by the PCD5013. PAGER TYPE single-phase single-phase single-phase single-phase any-phase any-phase any-phase any-phase all-phase; note 1 all-phase; note 1 all-phase; note 1 all-phase; note 1 single-phase single-phase single-phase single-phase any-phase all-phase; note 1 FRAME/PHASE EXTRACTION standard rules; Offset: 0 standard rules; Offset: 1 standard rules; Offset: 2 standard rules; Offset: 3 standard rules; Offset: 0 standard rules; Offset: 1 standard rules; Offset: 2 standard rules; Offset: 3 standard rules; Offset: 0 standard rules; Offset: 1 standard rules; Offset: 2 standard rules; Offset: 3 no frame extraction rules, phase-A no frame extraction rules, phase-B no frame extraction rules, phase-C no frame extraction rules, phase-D no frame extraction rules, any-phase no frame extraction rules, all-phase 1999 Apr 12 37 Philips Semiconductors Product specification FLEXTM roaming decoder II Table 33 Roaming CAPCODE character CHARACTER P Q R S DESCRIPTION non-roaming or single frequency pager no frame offset, follows the Traffic Management Flags frame offset BIW101, does not follow the Traffic Management Flags frame offset BIW101, follows the Traffic Management Flags CONFIGURATION OF USER ADDRESSES (ID = 78H, 80H TO 8FH) PCD5013 In this case, the host must disable the user address location(s) by clearing the corresponding user address enable (UAE) bit in the UAE packet before changing any of the bits in the corresponding address assignment packet. a: address location (Table 34). This specifies which address location is being configured. A zero in this field corresponds to address index zero (AI = 0) in the address packet received from the PCD5013 when an address is detected (Section 8.7.2). LA: long address (Table 34). When this bit is set, the address is configured as a long address. Both words of a long address must have this bit set. TOA: tone-only address (Table 34). When this bit is set, the PCD5013 considers this address a tone-only address and does not decode a vector word when the address is received. Both words of a long, tone only address must have this bit set. A: address word (Table 34). This is the 21-bit value of the address word (A20 = MSB). Valid FLEXTM messaging addresses or Network ID's must be used. For the conversion from a CAPCODE (Section 8.6.4). UAE: user address enable (Table 35). When a bit is set, the corresponding user address location is enabled. When it is cleared, the corresponding user address location is disabled. UAE0 corresponds to the user address location configured using a packet ID of 80H and UAE15 corresponds to the user address location configured using a packet ID of 8FH. In some instances, if an invalid FLEXTM messaging address is programmed, it is not detected even when the address is enabled. Value after reset = 0. 8.6.6 The PCD5013 has 16 user address locations which can be programmed as network IDs or as long or short addresses, which can be configured as priority and/or tone-only. After a reset all address locations are disabled. Short addresses and network IDs occupy a single location, long addresses occupy two locations. The first word of a long address must be in an even address location and the second word must be in the address index immediately following the first word. Address location containing long addresses of the 2-3 and 2-4 set (Section 8.6.3) must follow any address locations programmed as long addresses of the 1-2, 1-3 and 1-4 set. User addresses are programmed using the address assignment packets, and are enabled and disabled using the address enable packet. To allow easy reprogramming of user addresses without disrupting normal operation, the host can send address assignment packets while the PCD5013 is on. Table 34 Address assignment packet bit assignments (ID = 80H to 8FH) BYTE 3 2 1 0 BIT 7 1 0 A15 A7 BIT 6 0 LA A14 A6 BIT 5 0 TOA A13 A5 BIT 4 0 A20 A12 A4 BIT 3 a3 A19 A11 A3 BIT 2 a2 A18 A10 A2 BIT 1 a1 A17 A9 A1 BIT 0 a0 A16 A8 A0 Table 35 Address enable packet bit assignments (ID = 78H) BYTE 3 2 1 0 1999 Apr 12 BIT 7 0 0 UAE15 UAE7 BIT 6 1 0 UAE14 UAE6 BIT 5 1 0 UAE13 UAE5 BIT 4 1 0 UAE12 UAE4 38 BIT 3 1 0 UAE11 UAE3 BIT 2 0 0 UAE10 UAE2 BIT 1 0 0 UAE9 UAE1 BIT 0 0 0 UAE8 UAE0 Philips Semiconductors Product specification FLEXTM roaming decoder II 8.6.7 CONFIGURATION OF ASSIGNED FRAMES AND PAGER (ID = 20H TO 27H) 8.6.8 PCD5013 CONFIGURATION OF ASSIGNED PHASE COLLAPSE The assigned frame and collapse value determine the frames in which the decoding device typically looks for messages (other system factors can cause the decoding device to look in other frames in addition to the typical frames). The PCD5013 must be configured explicitly to receive all required frames by setting the associated assigned frame (AF) bits. For each enabled CAPCODE these are the base frame and the associated frames implied by the pager collapse value. For example if the PCD5013 has one enabled address and it is assigned to base frame 3 with a collapse value of 4, the AF bits for frames 3, 19, 35, 51, 67, 83, 99 and 115 should be set and the AF bits for all other frames should be cleared. When the PCD5013 is configured for manual collapse mode by setting the MCM bit in the Roaming Control Packet, the PCD5013 does not apply the received system collapse to the AF bits. The host should set the AF bits for all frames that should be decoded on all channels. For example, if frames 0 and 64 should be decoded on one channel and frames 4, 36, 68, and 100 should be decoded on another channel, all six of the corresponding AF bits should be set. The host can then change the receiver's carrier frequency after the PCD5013 decodes frames 0, 36, 64, and 100. There are 8 frame assignment packets each capable of assigning a range of 16 consecutive frame numbers. f: frame range, see Table 38 for location in the frame assignment packet and Table 36 for the AFs and values. The value determines which 16 frames out of a range of 128 correspond to the 16 AF bits in the packet. At least one of these bits must have been set when the PCD5013 is turned on by setting the ON bit in the control packet. Value after reset = 0. AF: assigned frame (Table 38). If a bit is set, the PCD5013 decodes the associated FLEXTM frame and scans its contents for enabled addresses. Value after reset = 0. The assigned phase is required only for single-phase devices. It determines the phase (A, B, C, or D) in which the messages are received. For details of phase calculation see Section 8.6.5. For details of programming the assigned phase see Section 8.4.7. Table 36 Frame assignment ranges f2 0 0 0 0 1 1 1 1 8.6.9 f1 0 0 1 1 0 0 1 1 f0 0 1 0 1 0 1 0 1 AF15 frame 127 frame 111 frame 95 frame 79 frame 63 frame 47 frame 31 frame 15 AF0 frame 112 frame 96 frame 80 frame 64 frame 48 frame 32 frame 16 frame 0 OPERATOR MESSAGING ADDRESS ENABLE PACKET (ID = 04H) The operator messaging address enable packet is used to enable and disable the built-in FLEXTM operator messaging addresses. Enabling and disabling operator messaging addresses does not affect on which frames the decoder IC decodes. To ensure that the correct frames are decoded, the host must modify the FF bits in the Control Packet or the AF bits in the Frame Assignment Packets. OAE: operator messaging address enable (Table 37). When a bit is set, the corresponding operator messaging address is enabled. When it is cleared, the corresponding operator messaging address is disabled. OAE0 to OAE15 corresponds to the hexadecimal operator messaging address values of 1F7810 through to 1F781F respectively. Value after reset = 0. Table 37 Operator messaging address enable packet bit assignments BYTE 3 2 1 0 BIT 7 0 0 OAE15 OAE7 BIT 6 0 0 OAE14 OAE6 BIT 5 0 0 OAE13 OAE5 BIT 4 0 0 OAE12 OAE4 BIT 3 0 0 OAE11 OAE3 BIT 2 1 0 OAE10 OAE2 BIT 1 0 0 OAE9 OAE1 BIT 0 0 0 OAE8 OAE0 1999 Apr 12 39 Philips Semiconductors Product specification FLEXTM roaming decoder II Table 38 Frame assignment packet bit assignments BYTE 3 2 1 0 8.7 8.7.1 BIT 7 0 0 AF15 AF7 BIT 6 0 0 AF14 AF6 BIT 5 1 0 AF13 AF5 BIT 4 0 0 AF12 AF4 BIT 3 0 0 AF11 AF3 BIT 2 f2 0 AF10 AF2 PCD5013 BIT 1 f1 0 AF9 AF1 BIT 0 f0 0 AF8 AF0 Call data packets GENERAL For long addresses, the address packet is only sent once with AI referring to the second word of the address. TOA: tone-only address (Table 39). This bit is set if the address was programmed as a tone-only address. No vector word is sent for tone-only addresses. This bit is never set for temporary or operator messaging addresses. WN: word number of vector (2 to 87 decimal) (Table 39). The location of the vector within this frame for the detected address. This value is invalid for this packet if the TOA bit is set. x: unused bits (Table 39). The value of these bits is not guaranteed. 8.7.3 VECTOR PACKETS (ID = 02H TO 57H) The PCD5013 sends data extracted from the FLEXTM signal to the host in SPI packets using the following packet types: * BIW packets which contain data transmitted in BIWs * Address packets which indicate that a call has been detected and give additional information about call attributes * Vector packets which indicate the call type and indicate which message word numbers (WN) are associated with the call * Message packets which contain the information contained within the message codewords of a call. For more information about the function of these packets within the FLEXTM data stream see Section 8.8. 8.7.2 ADDRESS PACKET (ID = 01H) Information from vector codewords in received calls is sent to the host in vector packets. For any address packet sent to the host (except tone-only addresses), a corresponding vector packet is always sent. The ID of the vector packet is the word number where the vector word was received in the frame. The host must associate vector packets with a call by searching for an address packet previously received on the same phase and with WN bits which match the ID of the vector packet. The vector type of a vector packet indicates the format of a call as one of: * Numeric (3 types) * Short message/tone-only * Hex/binary * Alphanumeric * Secure message * Short instruction. The numeric, hex/binary, alphanumeric, and secure message vector packets indicate the location and number of message word packets in the message field. If more than two bit errors are detected in the vector word (via BCH calculations, parity calculations, check character calculations, or value validation) the e bit is set and the message words are not sent. 40 Information from address codewords in received calls is sent to the host in address packets. If less than 3-bit errors are detected in a received address word and it matches an enabled address assigned to the PCD5013, the address packet is sent to the host processor. The address packet contains the call address, the location in the data stream of the associated vector, and other miscellaneous call data. PA: priority address (Table 39). This bit is set if the address was received as a priority address. p: phase (Table 39). This is the phase on which the address was detected (0 = A, 1 = B, 2 = C and 3 = D). LA: long address (Table 39). This bit is set if the address was programmed in the PCD5013 as a LA. AI: address index (Table 39). This index identifies which address was detected. Valid values are 00H to 0FH, corresponding to the 16 programmable address words and 80H to 8FH, corresponding to the 16 temporary addresses (Section 8.8.5). Values 144 through to 159 correspond to 16 operator messaging addresses. 1999 Apr 12 Philips Semiconductors Product specification FLEXTM roaming decoder II Table 39 Address packet bit assignments BYTE 3 2 1 0 8.7.4 BIT 7 0 PA AI7 TOA BIT 6 0 p1 AI6 WN6 BIT 5 0 p0 AI5 WN5 BIT 4 0 LA AI4 WN4 BIT 3 0 x AI3 WN3 BIT 2 0 x AI2 WN2 PCD5013 BIT 1 0 x AI1 WN1 BIT 0 1 x AI0 WN0 NUMERIC VECTOR PACKET WN: word number of vector (2 to 87 decimal) (Table 40). WN describes the location of the vector word in the frame. e: error (Table 40). Set if more than 2-bit errors are detected in the word, if the check character calculation fails after error correction has been performed, or if the vector value is determined to be invalid. p: phase (Table 40). This is the phase on which the vector was found (0 = A, 1 = B, 2 = C and 3 = D). x: unused bits (Table 40). The value of these bits is not guaranteed. V: vector type identifier (Table 41). Table 40 Numeric vector packet bit assignments BYTE 3 2 1 0 BIT 7 0 e x n0 BIT 6 WN6 p1 x b6 BIT 5 WN5 p0 K3 b5 K: first check bits of the message checksum (Table 40 and Section 8.8.7). n: number of message words in the message (Table 40), including the second vector word for long addresses, (000 = 1 word message, 001 = 2 word message, etc.). For long addresses, the first message word is located in the word location that immediately follows the associated vector. b: word number of message start in the message field (3 to 87 decimal) (Table 40). For long addresses, the word number indicates the location of the second message word. BIT 4 WN4 x K2 b4 BIT 3 WN3 x K1 b3 BIT 2 WN2 V2 K0 b2 BIT 1 WN1 V1 n2 b1 BIT 0 WN0 V0 n1 b0 Table 41 Numeric vector definitions V2 0 1 1 V1 1 0 1 V0 1 0 1 TYPE standard numeric special format numeric numbered numeric DESCRIPTION No special formatting of characters is specified. Formatting of the received characters is predetermined by special rules in the host (e.g. inserting spaces and dashes). Received information is numbered by the service provider to indicate all messages have been properly received. 1999 Apr 12 41 Philips Semiconductors Product specification FLEXTM roaming decoder II 8.7.5 SHORT MESSAGE/TONE-ONLY VECTOR PACKET PCD5013 t: message type (Tables 42 and 43). These bits define the meaning of the d bits in this packet. x: unused bits (Table 42). The value of these bits is not guaranteed. d: data bits whose definition depends on the value of t in this packet according to Table 43. Note that if this vector is received on a long address and the e bit in this packet is not set, the decoder sends a message packet from the word location immediately following the vector packet. Except for the short message on a non-network address (t = 0), all messages bits in the message packet are unused and should be ignored. V: vector type identifier, these bits set to 010 for a short message/tone-only vector (Table 42). WN: word number of vector (2 to 87 decimal) (Table 42). WN describes the location of the vector word in the frame. e: error (Table 42). Set if more than 2-bit errors are detected in the word, if the check character calculation fails after error correction has been performed, or if the vector value is determined to be invalid. p: phase (Table 42). This is the phase on which the vector was found (0 = A, 1 = B, 2 = C and 3 = D). Table 42 Short message/tone-only vector packet bit assignments BYTE 3 2 1 0 BIT 7 0 e x d5 BIT 6 WN6 p1 x d4 BIT 5 WN5 p0 d11 d3 BIT 4 WN4 x d10 d2 BIT 3 WN3 x d9 d1 BIT 2 WN2 V2 d8 d0 BIT 1 WN1 V1 d7 t1 BIT 0 WN0 V0 d6 t0 Table 43 Short message/tone-only vector definitions; note 1 t1 0 0 1 t0 0 1 0 d11 c3 s8 s1 d10 c2 s7 s0 d9 c1 s6 R0 d8 c0 s5 N5 d7 b3 s4 N4 d6 b2 s3 N3 d5 b1 s2 N2 d4 b0 s1 N1 d3 a3 s0 N0 d2 a2 S2 S2 d1 a1 S1 S1 d0 a0 S0 S0 DESCRIPTION first 3 numeric characters; note 2 8 sources (S) and 9 unused bits (s) 8 sources (S), message retrieval flag (R), message number (N) and 2 unused bits (s) spare message type 1 Notes 1 1. When this vector is sent in conjunction with a Network Address, the t1,to value `00' represents Network ID information. In this case the bit definitions are: T3 T2 T1 T0 M2 M1 M0 A4 A3 A2 A1 A0 Where T are Traffic Management Flags, M represents a multiplier and A is the service area. 2. For long addresses, an extra 5 characters are sent in the message packet immediately following the vector packet. t0 and t1 are also set to `00' when defining the last 12 bits of a Network Address. 1999 Apr 12 42 Philips Semiconductors Product specification FLEXTM roaming decoder II 8.7.6 HEX/BINARY, ALPHANUMERIC AND SECURE MESSAGE VECTORS PCD5013 b: word number of message start in the message field (Table 45). Valid values are 3 to 87 decimal. x: unused bits (Table 45). The value of these bits is not guaranteed. Note that for long addresses, the first message packet is sent from the word location immediately following the word location of the vector packet. The b bits indicate the second message word in the message field if one exists. Table 44 Non-numeric vector definitions V2 0 1 1 V1 0 0 1 V0 0 1 0 TYPE secure alphanumeric hex/binary V: vector type identifier (Table 44). WN: word number of vector (2 to 87 decimal) (Table 45). WN describes the location of the vector word in the frame. e: error (Table 45). Set if more than 2-bit errors are detected in the word, if the check character calculation fails after error correction has been performed, or if the vector value is determined to be invalid. p: phase (Table 45). This is the phase on which the vector was found (0 = A, 1 = B, 2 = C and 3 = D). n: number of message words in this frame (Table 45), including the first message word that immediately follows a long address vector. Valid values are 1 to 85 decimal. Table 45 Hex/binary, alphanumeric and secure message vector packet bit assignments BYTE 3 2 1 0 BIT 7 0 e x n0 BIT 6 WN6 p1 x b6 BIT 5 WN5 p0 n6 b5 BIT 4 WN4 x n5 b4 BIT 3 WN3 x n4 b3 BIT 2 WN2 V2 n3 b2 BIT 1 WN1 V1 n2 b1 BIT 0 WN0 V0 n1 b0 1999 Apr 12 43 Philips Semiconductors Product specification FLEXTM roaming decoder II 8.7.7 SHORT INSTRUCTION VECTOR PCD5013 i: instruction type (Tables 46 and 47). These bits define the meaning of the d bits in this packet. x: unused bits (Table 46). The value of these bits is not guaranteed. d: data bits whose definition depend on the value of the i bits in this packet according to Table 47. Note that if this vector is received on a long address and the e bit in this packet is not set, the decoder sends a message packet immediately following the vector packet. All message bits in the message packet are unused and should be ignored. V: these bits are set 001 for a short instruction vector. WN: word number of vector (2 to 87 decimal) (Table 46). WN describes the location of the vector word in the frame. e: error (Table 46). Set if more than 2-bit errors are detected in the word, if the check character calculation fails after error correction has been performed, or if the vector value is determined to be invalid. p: phase (Table 46). This is the phase on which the vector was found (0 = A, 1 = B, 2 = C and 3 = D). Table 46 Short instruction vector packet bit assignments BYTE 3 2 1 0 BIT 7 0 e x d4 BIT 6 WN6 p1 x d3 BIT 5 WN5 p0 d10 d2 BIT 4 WN4 x d9 d1 BIT 3 WN3 x d8 d0 BIT 2 WN2 V2 d7 i2 BIT 1 WN1 V1 d6 i1 BIT 0 WN0 V0 d5 i0 Table 47 Short instruction vector definitions i2 0 0 0 0 1 1 1 1 Notes 1. Assigned temporary address index a and associated frame number f (Section 8.8.5). 2. Refer to"FLEXTM Protocol specification G1.9". i1 0 0 1 1 0 0 1 1 i0 0 1 0 1 0 1 0 1 d10 a3 d10 a3 d9 a2 d9 a2 d8 a1 d8 a1 d7 a0 d7 a0 d6 f6 d6 f6 d5 f5 d5 N5 d4 f4 d4 N4 d3 f3 d3 N3 d2 f2 d2 N2 d1 f1 d1 N1 d0 f0 d0 N0 DESCRIPTION temporary address assignment, note 1 system event; note 2 temporary address with message sequence number; note 2 reserved reserved reserved reserved reserved for test 1999 Apr 12 44 Philips Semiconductors Product specification FLEXTM roaming decoder II 8.7.8 MESSAGE PACKETS (ID = 03H TO 57H) PCD5013 Only codewords containing the numeric message are to be transmitted. The space character CH is used to fill any unused 4-bit characters in the last word and zeros to fill any remaining partial characters. The checksum includes only the codewords comprising the shortened message, along with the space and fill characters used to fill in the last word. Table 48 Standard and alternate numeric character sets; Peoples Republic of China (PRC) option `on' and `off' CHARACTER B3 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 B2 0 0 0 0 1 1 1 1 0 0 0 0 1 1 1 1 B1 0 0 1 1 0 0 1 1 0 0 1 1 0 0 1 1 B0 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 PRC `on' 0 1 2 3 4 5 6 7 8 9 A B space C D E PRC `off' 0 1 2 3 4 5 6 7 8 9 spare U space - ] [ 8.7.8.1 General The message field follows the vector field in the FLEXTM protocol. It contains the message data, checksum information, and may contain fragment and message numbers (Sections 8.8.8 and 8.8.6). If the error bit of a vector word is not set and the vector word indicates that there are message words associated with the page, the message words are sent in message packets to the host. The ID of the message packet is the word number where the message word was received in the frame. WN: word number of message word (3 to 87 decimal) (Table 49). WN describes the location of the message word in the frame. e: error (Table 49). Set if more than 2-bit errors are detected in the word. p: phase (Table 49). This is the phase on which the vector was found (0 = A, 1 = B, 2 = C and 3 = D). i: these are the information bits of the message word (Table 49). The definition of these i bits depends on the vector type and which word of the message is being received. 8.7.8.2 Numeric Message FLEXTM numeric messages are encoded using the 4-bit BCD encoded characters sets described in Table 48. Characters are placed in codewords along with additional information about the message as described in Tables 50 and 51 and the following definitions. The 4-bit numeric characters of the message are designated as letters a, b, c, d, ... z, A, B etc. Table 49 Message packet bit assignments BYTE 3 2 1 0 BIT 7 0 e i15 i7 BIT 6 WN6 p1 i14 i6 BIT 5 WN5 p0 i13 i5 BIT 4 WN4 i20 i12 i4 BIT 3 WN3 i19 i11 i3 BIT 2 WN2 i18 i10 i2 BIT 1 WN1 i17 i9 i1 BIT 0 WN0 i16 i8 i0 1999 Apr 12 45 Philips Semiconductors Product specification FLEXTM roaming decoder II K: least significant 2 bits of 6-bit message checksum (Tables 50 and 51), most significant 4 bits are in the vector word. See Section 8.8.7 for a description of message checksums. N: message number (Table 51). See Section 8.8.8 for a description of message numbering. R: message retrieval flag (Table 51). When this bit is set, the pager expects this message to be numbered. See Section 8.8.8 for a description of message numbering. PCD5013 S: special format, (Table 51). In the numbered message format, when this bit is set, a special display format should be used. Spaces and dashes, specified by the host, are inserted into the received message to ease reading of the message. This feature may avoid the transmission of an additional word on the channel. The actual format is undefined in FLEXTM and may be determined by the manufacturer. Table 50 Standard (V = 011) or special format (V = 100) 4, 10, 15, 20, 25, 31, 36, or 41 characters MESSAGE WORD 1st 2nd 3rd 4th 5th 6th 7th 8th i0 K4 e3 k0 q1 v2 B3 H0 i1 K5 f0 k1 q2 v3 C0 H1 i2 a0 f1 k2 q3 w0 C1 H2 i3 a1 f2 k3 r0 w1 C2 H3 i4 a2 f3 l0 r1 w2 C3 I0 O1 i5 a3 g0 l1 r2 w3 D0 I1 O2 i6 b0 g1 l2 r3 y0 D1 I2 O3 i7 b1 g2 l3 s0 y1 D2 I3 P0 i8 b2 g3 s1 y2 D3 J0 P1 i9 b3 h0 s2 y3 E0 J1 P2 i10 c0 h1 s3 z0 E1 J2 P3 i11 c1 h2 t0 z1 E2 J3 Q0 i12 c2 h3 n0 t1 z2 E3 V0 Q1 i13 c3 i0 n1 t2 z3 F0 V1 Q2 i14 d0 i1 n2 t3 A0 F1 V2 Q3 i15 d1 i2 n3 u0 A1 F2 V3 T0 i16 d2 i3 o0 u1 A2 F3 L0 T1 i17 d3 j0 o1 u2 A3 G0 L1 T2 i18 e0 j1 o2 u3 B0 G1 L2 T3 i19 e1 j2 o3 v0 B1 G2 L3 U0 i20 e2 j3 q0 v1 B2 G3 M0 U1 m0 m1 m2 m3 M1 M2 M3 O0 Table 51 Numbered (V = 111) 2, 8, 13, 18, 23, 29, 34, or 39 numeric characters MESSAGE WORD 1st 2nd 3rd 4th 5th 6th 7th 8th i0 K4 c3 i0 n1 t2 z3 F0 V1 i1 K5 d0 i1 n2 t3 A0 F1 V2 i2 N0 d1 i2 n3 u0 A1 F2 V3 i3 N1 d2 i3 o0 u1 A2 F3 L0 i4 N2 d3 j0 o1 u2 A3 G0 L1 i5 N3 e0 j1 o2 u3 B0 G1 L2 i6 N4 e1 j2 o3 v0 B1 G2 L3 i7 N5 e2 j3 q0 v1 B2 G3 i8 R0 e3 k0 q1 v2 B3 H0 i9 S0 f0 k1 q2 v3 C0 H1 i10 a0 f1 k2 q3 w0 C1 H2 i11 a1 f2 k3 r0 w1 C2 H3 i12 a2 f3 l0 r1 w2 C3 I0 O1 i13 a3 g0 l1 r2 w3 D0 I1 O2 i14 b0 g1 l2 r3 y0 D1 I2 O3 i15 b1 g2 l3 s0 y1 D2 I3 P0 i16 b2 g3 s1 y2 D3 J0 P1 i17 b3 h0 s2 y3 E0 J1 P2 i18 c0 h1 s3 z0 E1 J2 P3 i19 c1 h2 t0 z1 E2 J3 Q0 i20 c2 h3 n0 t1 z2 E3 V0 Q1 m0 m1 m2 m3 M0 M1 M2 M3 O0 1999 Apr 12 46 Philips Semiconductors Product specification FLEXTM roaming decoder II 8.7.8.3 Alphanumeric Message PCD5013 Where symbolic characters (e.g. Chinese, Kanji etc.) are being transmitted, special rules for fragment and message termination are defined in Section 8.8.6.1. Each 7-bit field, starting with the second character of the second word in the message (first character of the second word in all remaining fragments), represents standard ASCII (ISO 646-1983E) characters with options for certain international characters. FLEXTM alphanumeric messages are encoded using the 7-bit encoded alphanumeric character set defined in Table 52. Characters are placed in codewords along with additional information about the message as described in Tables 53 and 54 and the following definitions. The 7-bit characters of the message are designated lower case letters a, b, c, d, etc. Alphanumeric messages can be sent as fragments. See Section 8.8.6 for a description of message fragmentation. Control characters that are not acted upon by the pager are ignored in the display process (do not require display space) but are stored in memory for possible download to an external device. The ASCII character ETX (03H) should be used to fill any unused 7-bit characters in a word. Table 52 FLEXTM alphanumeric character set LEAST SIGNIFICANT 4 BITS OF CHARACTER (HEX) 0 1 2 3 4 5 6 7 8 9 A B C D E F MOST SIGNIFICANT 3 BITS OF CHARACTER (HEX) 0 NUL SOH STX ETX EOT ENQ ACK BEL BS TAB LF VT FF CR SO SI 1 DLE DC1 DC2 DC3 DC4 NAK SYN ETB CAN EM SUB ESC FS GS RS US 2 SP ! " # $ % & ' ( ) * + , . / 3 0 1 2 3 4 5 6 7 8 9 : ; < = > ? 4 @ A B C D E F G H I J K L M N O 5 P Q R S T U V W X Y Z [ \ ] ^ _ 6 ` a b c d e f g h i j k l m n o 7 p q r s t u v w x y z { } ~ DEL 1999 Apr 12 47 Philips Semiconductors Product specification FLEXTM roaming decoder II K: 10-bit fragment checksum (Tables 53 and 54). See Section 8.8.7 for a description of message checksum. C: 1-bit message continued flag (Tables 53 and 54). When this bit is set, fragments of this message are to be expected in following frames. See Section 8.8.6 for a description of message fragmentation. F: 2-bit message fragment number (Tables 53 and 54). This is a modulo 3 message fragment number which is incremented by 1 in successive message fragments. See Section 8.8.6 for a description of message fragmentation. N: message number (Tables 53 and 54). See Section 8.8.8 for a description of message numbering. M: 1-bit mail drop flag (Table 53). When this bit is set, it indicates the message is to be stored in a special area in memory and is written over existing data automatically in that memory space. Table 53 Vector type V = 101 first fragment MESSAGE WORD 1st 2nd 3rd 4th 5th ... nth i i i i i i i i i i i i i i i i i i i0 K0 S0 c0 f0 i0 i1 K1 S1 c1 f1 i1 i2 K2 S2 c2 f2 i2 i3 K3 S3 c3 f3 i3 i4 K4 S4 c4 f4 i4 i5 K5 S5 c5 f5 i5 i6 K6 S6 c6 f6 i6 i7 K7 a0 d0 g0 j0 i8 K8 a1 d1 g1 j1 i9 K9 a2 d2 g2 j2 i10 C0 a3 d3 g3 j3 i11 F0 a4 d4 g4 j4 i12 F1 a5 d5 g5 j5 i13 N0 a6 d6 g6 j6 i14 N1 b0 e0 h0 k0 i15 N2 b1 e1 h1 k1 i16 N3 b2 e2 h2 k2 PCD5013 R: message retrieval flag (Table 53). When this bit is set, the pager expects this message to be numbered. See Section 8.8.8 for a description of message numbering. S: 7-bit signature field (Table 53). The signature is defined to be the 1's complement of the binary sum over the total message (all fragments). 7 bits at a time are taken (on alpha character boundary) starting with the first 7 bits directly following the signature field, a6a5a4a3a2a1a0, b6b5b4b3b2b1b0, etc. The 7 LSBs of the result are transmitted as the message signature. U, V: fragmentation control bits (Table 54). This field exists in all fragments except the first fragment. It is used to support character position tracking in each fragment when symbolic characters (character made up of 1, 2 or 3 ASCII characters) are transmitted using the alphanumeric message type. The default value is 0,0. See Section 8.8.6.1 for a description of fragment control. i17 N4 b3 e3 h3 k3 i18 N5 b4 e4 h4 k4 i i19 R0 b5 e5 h5 k5 i i20 M0 b6 e6 h6 k6 i Table 54 Vector type V = 101 other fragments MESSAGE WORD 1st 2nd 3rd 4th 5th ... nth i i i i i i i i i i i i i i i i i i i i i i0 K0 a0 d0 g0 j0 i1 K1 a1 d1 g1 j1 i2 K2 a2 d2 g2 j2 i3 K3 a3 d3 g3 j3 i4 K4 a4 d4 g4 j4 i5 K5 a5 d5 g5 j5 i6 K6 a6 d6 g6 j6 i7 K7 b0 e0 h0 k0 i8 K8 b1 e1 h1 k1 i9 K9 b2 e2 h2 k2 i10 C0 b3 e3 h3 k3 i11 F0 b4 e4 h4 k4 i12 F1 b5 e5 h5 k5 i13 N0 b6 e6 h6 k6 i14 N1 c0 f0 i0 l0 i15 N2 c1 f1 i1 l1 i16 N3 c2 f2 i2 l2 i17 N4 c3 f3 i3 l3 i18 N5 c4 f4 i4 l4 i19 U0 c5 f5 i5 l5 i20 V0 c6 f6 i6 l6 1999 Apr 12 48 Philips Semiconductors Product specification FLEXTM roaming decoder II 8.7.8.4 Hex/binary message PCD5013 R: message retrieval flag (Table 55). When this bit is set, the pager expects this message to be numbered. See Section 8.8.8 for a description of message numbering. s: 5-bit field reserved for future use (Table 55). Default value = 00000. M: 1-bit mail drop flag, see Table 55. When this bit is set, the message is to be stored in a special area in memory to overwrite existing data in the same memory space. D: 1-bit display direction field (Table 55). D = 0 display left to right, D = 1 display right to left (valid only when data sent as characters i.e. blocking length not equal 0001). B: 4-bit blocking length (Table 55). Indicates bits per character. B3B2B1B0 = 0001 = 1-bit per character (binary/transparent data), 1111 = 15 bits per character, 0000 = 16 bits per character. Data with a blocking length other than 1 is assumed to be displayed on a character by character basis (default value = 0001). Note: Tables 55 and 56 show B = 4-bit blocking length. S: 8-bit signature field (Table 55). The 1's complement of the binary sum, taken 8 bits at a time, over the total message prior to formatting into fragments. The first 8 bits following the signature field are summed with the following 8 bits, b3b2b1b0a3a2a1a0 + d3d2d1d0c3c2c1c0, etc. continuing to the last valid data bit in the last word of the last fragment (the sum does not include termination bits). The 8 LSBs of the result are inverted (1's complement) and transmitted as the message signature. FLEXTM hexadecimal/binary messages may be encoded using any word size (blocking length) in the range 1 to 16 bits. Words are placed in codewords along with additional information about the message as described in Tables 55 and 56 and these definitions. The message data in Tables 55 and 56 have blocking lengths of 4 bits; words are designated lower case letters a, b, c, d etc. Hexadecimal/binary messages can be sent as fragments. See Section 8.8.6 for a description of message fragmentation. Messages and message fragments are terminated, or interrupted in the case of a non-terminating fragment, on the last full character boundary in the last codeword. Unused bits are cleared if the last valid data bit is logic 1, or set if the last valid data bit is logic 0. If the terminating fragment exactly fills its last codeword, an additional codeword is sent to indicate the location of the last character. This codeword is filled with logic 0s if the last valid data bit is logic 1 and filled with logic 1s if the last valid data bit is logic 0. Fields K to N make up the first word of a message and the first word of every fragment in a long message. K: 12-bit fragment checksum (Tables 55 and 56). See Section 8.8.7 for a description of message checksums. C: 1-bit message continued flag (Tables 55 and 56). When this bit is set, fragments of this message are to be expected in following frames. See Section 8.8.6 for a description of message fragmentation. F: 2-bit message fragment number (Tables 55 and 56). This is a modulo 3 message fragment number which is incremented by 1 in successive message fragments. See Section 8.8.6 for a description of message fragmentation. N: message number (Tables 55 and 56). See Section 8.8.8 for a description of message numbering. H: 1-bit header message flag (Table 55). It is a header message only when this bit is set, otherwise it is a data message. A header message is a displayable tag associated with a non-displayable data message. The header message (which is sent first) and the data message, both have the same message number. The second codeword of the first fragment of a hex/binary message contains fields R to S. These fields are only transmitted in the first fragment of a message. 8.7.8.5 Secure message FLEXTM secure messages are encoded using the 7-bit FLEXTM alphanumeric character set (Section 8.7.8.3). These characters are placed in codewords along with additional information about the message as described in Table 57 and the following definitions. In Table 57, 7-bit characters of the message are designated lower case letters a, b, c, d etc. Secure messages follow the same fragmentation and termination rules as alphanumeric messages (Section 8.7.8.3). K: 10-bit fragment checksum (Table 57). See Section 8.8.7 for a description of message checksums. C: 1-bit message continued flag (Table 57). When this bit is set, fragments of this message are to be expected in following frames. See Section 8.8.6 for a description of message fragmentation. 1999 Apr 12 49 Philips Semiconductors Product specification FLEXTM roaming decoder II F: 2-bit message fragment number (Table 57). This is a modulo 3 message fragment number which is incremented by 1 in successive message fragments. See Section 8.8.6 for a description of message fragmentation. Table 55 Vector type V = 110 first fragment MESSAGE WORD 1st 2nd 3rd 4th 5th 6th ... nth i i i i i i i i i i i i i i i i i i i0 K0 R0 a0 f1 k2 q3 i1 K1 M0 a1 f2 k3 r0 i2 K2 D0 a2 f3 l0 r1 i3 K3 H0 a3 g0 l1 r2 i4 K4 B0 b0 g1 l2 r3 i5 K5 B1 b1 g2 l3 s0 i6 K6 B2 b2 g3 s1 i7 K7 B3 b3 h0 s2 i8 K8 s0 c0 h1 s3 i9 i10 i11 i12 i13 F0 S0 d1 i2 n3 u0 i14 F1 S1 d2 i3 o0 u1 i15 N0 S2 d3 j0 o1 u2 i16 N1 S3 e0 j1 o2 u3 PCD5013 N: message number (Table 57). See Section 8.8.8 for a description of message numbering. s: spare bits (Table 57), are not used and are set to 0. i17 N2 S4 e1 j2 o3 v0 i18 N3 S5 e2 j3 q0 v1 i i19 N4 S6 e3 k0 q1 v2 i i20 N5 S7 f0 k1 q2 v3 i K9 K10 K11 C0 s1 c1 h2 t0 s2 c2 h3 n0 t1 s3 c3 i0 n1 t2 s4 d0 i1 n2 t3 m0 m1 m2 m3 Table 56 Vector type V = 110 all other fragments MESSAGE WORD 1st 2nd 3rd 4th 5th ... nth i i i i i i i i i i i i i i i i i i i i i i0 K0 a0 f1 k2 q3 i1 K1 a1 f2 k3 r0 i2 K2 a2 f3 l0 r1 i3 K3 a3 g0 l1 r2 i4 K4 b0 g1 l2 r3 i5 K5 b1 g2 l3 s0 i6 K6 b2 g3 s1 i7 K7 b3 h0 s2 i8 K8 c0 h1 s3 i9 i10 i11 i12 i13 F0 d1 i2 n3 u0 i14 F1 d2 i3 o0 u1 i15 N0 d3 j0 o1 u2 i16 N1 e0 j1 o2 u3 i17 N2 e1 j2 o3 v0 i18 N3 e2 j3 q0 v1 i19 N4 e3 k0 q1 v2 i20 N5 f0 k1 q2 v3 K9 K10 K11 C0 c1 h2 t0 c2 h3 n0 t1 c3 i0 n1 t2 d0 i1 n2 t3 m0 m1 m2 m3 Table 57 Vector type V = 000 all fragments MESSAGE WORD 1st 2nd 3rd 4th 5th ... nth i i i i i i i i i i i i i i i i i i i i i i0 K0 a0 d0 g0 j0 i1 K1 a1 d1 g1 j1 i2 K2 a2 d2 g2 j2 i3 K3 a3 d3 g3 j3 i4 K4 a4 d4 g4 j4 i5 K5 a5 d5 g5 j5 i6 K6 a6 d6 g6 j6 i7 K7 b0 e0 h0 k0 i8 K8 b1 e1 h1 k1 i9 K9 b2 e2 h2 k2 i10 C0 b3 e3 h3 k3 i11 F0 b4 e4 h4 k4 i12 F1 b5 e5 h5 k5 i13 N0 b6 e6 h6 k6 i14 N1 c0 f0 i0 l0 i15 N2 c1 f1 i1 l1 i16 N3 c2 f2 i2 l2 i17 N4 c3 f3 i3 l3 i18 N5 c4 f4 i4 l4 i19 s0 c5 f5 i5 l5 i20 s1 c6 f6 i6 l6 1999 Apr 12 50 Philips Semiconductors Product specification FLEXTM roaming decoder II 8.7.9 BLOCK INFORMATION WORD PACKET (ID = 00H) PCD5013 System providers supporting local time transmissions are required to transmit at least one time related BIW in each phase transmitted in frame 0, cycle 0. The time transmitted is the local time for the transmitted time zone and refers to the actual time at the leading edge of the first bit of sync 1 of frame 0 of the current cycle. See Tables 58, 59, and 60 and the following bit definitions of the time related BIWs. e: error (Table 58). Set if more than 2-bit errors are detected in the word or if the check character calculation fails after error correction has been performed. p: phase (Table 58), is the phase on which the BIW was found (0 = A, 1 = B, 2 = C and 3 = D). x: unused bits (Table 58). Their value is not guaranteed. f: word format type (Table 58). The value of these bits modify the meaning of the s bits in this packet as described in Table 59. s: BIW information bits (Table 58). The definition of these bits depend on the f bits in this packet. The FLEXTM protocol allows systems to transmit time information using block information words. The information carried in a BIW depends on the BIW word format (Table 58). The first BIW of each phase, carrying information about the frame structure, is used internally by the PCD5013 and is never transmitted to the host with the exception of the system collapse which is sent to the host when the PCD5013 is in manual collapse mode. The PCD5013 can be configured to send all time and date BIWs (BIW001, BIW010 and BIW101) to the host by setting the SBI bit in the control packet, see Section 8.4.7. All block information words 2-4 can be optionally sent to the host by setting the ABI bit in the roaming control packet. When the SBI or ABI bit is set and a BIW is received with an uncorrectable number of bit errors, the PCD5013 sends the BIW to the host indicating that the codeword was received in error (regardless of the BIW word format). The PCD5013 does not support decoding of vector and message words associated with the data/system message BIW101. Table 58 BIW packet bit assignments BYTE 3 2 1 0 BIT 7 0 e x s7 BIT 6 0 p1 x s6 BIT 5 0 p0 s13 s5 BIT 4 0 x s12 s4 BIT 3 0 x s11 s3 BIT 2 0 f2 s10 s2 BIT 1 0 f1 s9 s1 BIT 0 0 f0 s8 s0 Table 59 BIW definitions f2 0 0 0 0 1 1 1 1 Notes 1. Decoded only if ABI bit is set. 2. Decoded only if SBI or ABI bit is set. f1 0 0 1 1 0 0 1 1 f0 0 1 0 1 0 1 0 1 s13 s12 s11 s10 i8 m3 S2 i7 m2 S1 i6 m1 S0 i5 m0 M5 s9 i4 d4 M4 s8 i3 d3 M3 s7 i2 d2 M2 s6 i1 d1 M1 s5 i0 d0 M0 s4 C4 Y4 H4 s3 C3 Y3 H3 s2 C2 Y2 H2 s1 C1 Y1 H1 s0 DESCRIPTION C0 Local ID, Coverage Zone(1) Y0 month/day/year(2) H0 second/minute/hour(2) Reserved by FLEXTM protocol for future use (1) Reserved by FLEXTM protocol for future use (1) z9 c8 z8 c7 z7 c6 z6 c5 z5 c4 z4 c3 z3 c2 z2 c1 z1 c0 z0 T4 0 T3 1 T2 0 T1 X T0 system message; (2) Reserved by FLEXTM protocol for future use (1) Country Code, Traffic Management Flags(1) 1999 Apr 12 51 Philips Semiconductors Product specification FLEXTM roaming decoder II i: Local ID (Table 59). A Local ID along with the Coverage Zone, Country Code and Traffic Management Flags define a specific simulcast coverage area for SSID roaming. C: Coverage Zone (Table 59). A Coverage Zone along with a Local ID, Country Code and Traffic Management Flags define a specific simulcast coverage area for SSID roaming. m: month field (Table 59). 0001 to 1100 binary correspond to January to December in month order. d: day field (Table 59). 00001 to 11111 binary correspond to 1 to 31 days in the month. Y: year field (Table 59). This represents the year with modulo 32 arithmetic. 00000 to 11111 binary representing years 1994 to 2025 and 2026 to 2057. S: seconds field (Table 59). This represents a coarse value of the seconds field. These bits represent the seconds in 18 minute (7.5 s) increments. 000 to 111 binary correspond to 0 to 52.5 seconds. M: minute field (Table 59). 000000 to 111011 binary correspond to 0 to 59 minutes. PCD5013 H: hour field (Table 59). 00000 to 10111 binary correspond to 0 to 23 hours. L: daylight savings time (Table 59). When this bit is set, the time being transmitted is local standard time. When it is clear, the time being transmitted is daylight savings time. z: time zone (Table 59). These bits indicate the time zone for the time which is being transmitted. The offset from GMT is the offset for local standard time. Table 60 describes the values for z. c: Country code (Table 59) identified in the CCITT (ITU-T) Standard E.212, Annex A. T: Traffic management flags (Table 59). indicate a possible assignment of any combination of 4 groups of traffic to an RF channel. Each roaming subscriber unit, after finding an RF channel which matches its programmed Local ID, Coverage Zone and Country Code responds to only one of the 4 Traffic Management Flags. When one or more of the transmitted Traffic Management Flags are set to O, subscriber units assigned to those traffic groups must find another RF channel with the same LID, Coverage Zone and Country Code information with its assigned Traffic Flag set to 1. Table 60 Time zone values z4 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 z3 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 z2 0 0 0 0 1 1 1 1 0 0 0 0 1 1 1 1 z1 0 0 1 1 0 0 1 1 0 0 1 1 0 0 1 1 z0 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 TIME ZONE GMT GMT + 01:00h GMT + 02:00h GMT + 03:00h GMT + 04:00h GMT + 05:00h GMT + 06:00h GMT + 07:00h GMT + 08:00h GMT + 09:00h GMT + 10:00h GMT + 11:00h GMT + 12:00h GMT + 03:30h GMT + 04:30h GMT + 05:30h z4 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 z3 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 z2 0 0 0 0 1 1 1 1 0 0 0 0 1 1 1 1 z1 0 0 1 1 0 0 1 1 0 0 1 1 0 0 1 1 z0 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 TIME ZONE reserved GMT + 05:45h GMT + 06:30h GMT + 09:30h GMT - 03:30h GMT - 11:00h GMT - 10:00h GMT - 09:00h GMT - 08:00h GMT - 07:00h GMT - 06:00h GMT - 05:00h GMT - 04:00h GMT - 03:00h GMT - 02:00h GMT - 01:00h 1999 Apr 12 52 Philips Semiconductors Product specification FLEXTM roaming decoder II 8.8 8.8.1 Message reception FLEXTM SIGNAL STRUCTURE PCD5013 The synchronization portion consists of: a first sync signal at 1600 bps; a frame information word having the frame number 0 to 127 (7 bits) and the cycle number 0 to 14 (4 bits); and a second sync signal at the data rate of the interleaved portion. The block information field contains BIWs. These can be used for determining time and date information and certain paging system information. The address field contains addresses assigned to paging devices. Addresses are used to identify information sent to individual paging devices and/or groups of paging devices. Information in the FLEXTM signal may indicate that an address is a priority address. An address may be either a short (one word) address or a long (two word) address. An address may be a tone-only address in which case there is no additional information associated with the address. If an address is not a tone-only address, then there is an associated vector word in the vector field. Information in the FLEXTM signal indicates the location of the vector word in the vector field associated with the address. A pager may perform battery saving at the end of the address field when its address(es) is not detected. The vector field consists of a series of vector words. Depending upon the type of message, a vector word (or words in the case of a long address) may either contain all of the information necessary for the message, or indicate the location of message words in the message field comprising the message information. Short addresses have one associated vector word in the vector field. Long addresses have one associated vector word in the vector field directly followed by the first message codeword of the call. The message field consists of a series of information words containing message information. The message information may be formatted in ASCII, BCD or binary depending upon the message type. The FLEXTM signal transmitted on the radio channel (see Fig.18) consists of a series of four minute cycles, each cycle having 128 frames at 1.875 seconds per frame. A pager may be assigned to process any number of the frames. Battery saving is performed for frames which are not assigned. The FLEXTM signal can assign additional frames to the pager using collapse, fragmentation, temporary addressing or carry-on information within the FLEXTM signal. Each FLEXTM frame has a synchronization portion followed by an eleven block data portion, each block lasting 160 milliseconds. The synchronization portion indicates the rate at which the data portion is transmitted, 1600, 3200 or 6400 bits per second (bps). The 1600 bps rate is transmitted at 1600 symbols per second (sps) using 2 level FSK modulation and consists of a single phase of information at 1600 bps, phase-A. The 3200 bps rate is transmitted at either 1600 sps using 4 level FSK modulation or 3200 sps using 2 level FSK modulation and consists of two concurrent phases of information at 1600 bps, phase-A and phase-C. The 6400 bps rate is transmitted at 3200 sps using 4 level FSK modulation and consists of four concurrent phases of information at 1600 bps (phase-A, -B, -C and -D). Each block has eight interleaved words per phase, thus there are 88 codewords (numbered 0 to 87) per phase in every frame. Each word has information contained within an error correcting code which allows for bit error correction and detection. The 88 words in each phase are organized into a block information field, an address field, a vector field, a message field, and an idle field. The boundaries between the fields are independent of the block boundaries. Furthermore, at 3200 and 6400 bps, the information in one phase is independent of the information in a concurrent phase, and the boundaries between the fields of one phase are unrelated to the boundaries between the fields in a concurrent phase. 1999 Apr 12 53 Philips Semiconductors Product specification FLEXTM roaming decoder II 8.8.2 FLEXTM ROAMING STRUCTURE PCD5013 NIDs and SSIDs are referred to as Roaming IDs. In addition pagers may be programmed to search for calls on a channel without finding an SSID or an NID in order to receive calls on that RF channel. In this case the Roaming ID associated with the channel is programmed within the pager as having ANY ID. The FLEXTM paging protocol defines two methods for supporting roaming pagers: * Simulcast System identification (SSID) roaming, where pagers scan a pre-programmed set of channels and identify each simulcast area which is to be included in the desired roaming area * Network identification (NID) roaming where pagers examine all frequencies within the subscriber units's range for the presence of a marker (NID). The NID indicates whether the channel is affiliated with the desired roaming network. A Simulcast System Identifier (SSID) is carried in the Block Identification Field. A SSID is composed of a Local Identifier (LID), a Coverage Zone, a Country Code and Traffic Management Flags. These components define a simulcast area which is unique worldwide. An LID is unique within a Country Code and cannot be reassigned to another operator in any paging RF band. A Network Identifier (NID) is carried in the address and vector fields. NIDs are unique within an RF band and are composed of a Network Address, a Service Area Identifier, a Multiplier and Traffic Management Flags. An RF channel may combine roaming traffic from several different Service Providers by carrying their respective NIDs. 8.8.2.1 Example Roaming System Figure 17 shows six RF frequencies servicing three cities. NID1 is used to identify a network covering all three cities and SSIDs A, B and C identify the specific simulcast areas covering cities A, B and C. In city C, the large amount of traffic has resulted in the service provider activating additional RF channels identified as a, b, d, e and f. In this example, the pager is assigned Roaming IDs as follows: SSIDC NID1 traffic management group 2 (0100) Thus the pager will monitor frequencies as follows: fb when in the area of city A fc when in the area of city B fd when in the area of city C. For further information on FLEXTM Roaming, see the "FLEXTM specification G1.9". handbook, full pagewidth NID1 - 0011 SSIDC - 0000 NID1 - 0000 SSIDC - 1000 NID1 - 0000 SSIDC - 0100 NID1 - 1111 SSIDB - 1111 NID1 - 1111 SSIDA - 1111 NID1 - 0000 SSIDC - 0010 NID1 - 1100 SSIDC - 0001 ff fe fd fc fb fa City A City B City C Pager is assigned SSIDC as Home with NID1 active away from Home. Pager is assigned to TMG 2 (0100 - 3rd flag from right). Frequency list contains fa, fb, fc, fd, fe and ff. MGL555 Fig.17 Roaming system example. 1999 Apr 12 54 Philips Semiconductors Product specification FLEXTM roaming decoder II PCD5013 handbook, full pagewidth 15 cycles (1 hour) cycle 0 cycle 1 cycle 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cycle 13 cycle 14 1 cycle (4 minutes) = 128 frames frame 0 frame 1 frame 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . frame 126 frame 127 1 frame (1.875 seconds) = sync + 11 blocks sync block 0 block 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . block 9 block 10 sync (115 ms) sync 1 frame info sync 2 interleaved block (160 ms) 8 x 32 bits @ 1600 bps 16 x 32 bits @ 3200 bps 32 x 32 bits @ 6400 bps 8 + 32 bits @ 1600 bps 48 + 32 bits @ 3200 bps 128 + 32 bits @ 6400 bps 32 bits @ 1600 bps (20 ms) 2 - level FM 2 or 4 level FM 4 - level FM MGK469 (25 ms) 112 bits @ 1600 bps (70 ms) Fig.18 FLEXTM signal structure. 1999 Apr 12 55 Philips Semiconductors Product specification FLEXTM roaming decoder II 8.8.3 MESSAGE BUILDING PCD5013 Tables 61 and 62 show an example of receiving three messages (possibly portions of fragmented or group messages), and two BIW packets in the first two blocks of a 2 phase 3200 bps FLEXTM frame in case of an any-phase pager. Table 61 shows the block number, word number and word content of both phase-A and phase-C (subscripts indicate the call number). In a 6400 bps FLEXTM frame, there would be four phases: A, B, C and D; in a 1600 bps signal there would be only phase-A. Table 62 shows the sequence of packets transmitted to the host. Table 62 PCD5013 packet sequence PACKET PHASE 1 2 3 A A A PACKET WORD TYPE NO. address address vector 7 8 7 COMMENT note 1 note 1 pointer to phase-A word 9 note 2 note 2 note 1 pointer to phase-A word 12 mess1 (cw 1) mess1 (cw 2) mess1 (cw 3) mess2 (cw 1) mess2 (cw 2) mess2 (cw 3) mess2 (cw 4) pointer to phase-A word 14 mess3 (cw 1) mess3 (cw 2) mess3 (cw 3) The PCD5013 sends data from the FLEXTM signal to the host in packets. Data is transmitted one block at a time, and one phase at a time. For a 2 phase transmission, information in block 0 phase-A is converted into packets and sent to the host, then information in block 0 phase-C is sent to the host followed by information in block 1 phase-A and then information in block 1 phase-C etc. Codewords for different calls may therefore be interleaved, so the host must use the phase and word number embedded in each packet to associate that packet with a particular call. The phase and word number of the vector packet provides a unique key which allows the host to associate all the data for a particular call within a frame. The host must then use information embedded in the vector word to calculate what message word locations are associated with the vector. Table 61 FLEXTM transmission sequence BLOCK WORD 0 1 2 0 3 4 5 6 7 8 9 10 11 1 12 13 14 15 Notes 1. Phases begin with BIW1, which is not sent to the host. 2. Codewords not addressed to the pager. 3. Vector for long address indicates the location of the second and third message words. 4. For long addresses, the first message word immediately follows the vector. mess2 (cw 1) mess2 (cw 2) mess2 (cw 3) mess2 (cw 4) PHASE-A BIW1; note 1 addr; note 2 addr; note 2 addr1 addr2 vect; note 2 vect; note 2 vect1 vect2 mess1 (cw 1) mess1 (cw 2) mess1 (cw 3) BIW BIW addr; note 2 addr; note 2 long addr3 (cw 1) long addr3 (cw 2) addr; note 2 vect; note 2 vect; note 2 vect3; note 3 mess3 (cw 1); note 4 mess; note 2 mess; note 2 mess3 (cw 2) mess3 (cw 3) PHASE-C BIW1; note 1 4 5 6 7 C C C A BIW BIW long address vector n.a. n.a. 10 8 8 9 10 11 12 13 14 15 A A A A A A A C message 9 message 10 message 11 message 12 message 13 message 14 message 15 vector 10 16 17 18 Notes C C C message 11 message 14 message 15 1. Word number in an address is that of the corresponding vector. 2. BIW sent if BIW reception enabled by SBI bit in the control packet. 1999 Apr 12 56 Philips Semiconductors Product specification FLEXTM roaming decoder II 8.8.4 ALL FRAME MODE (ID = 03H) PCD5013 AFM remains active until the host determines that no further data can be sent to it outside programmed frames, i.e: * The TAE counters are all zero indicating that no further temporary message data is expected * The AFM counter is zero indicating that no further data is expected for fragmented messages * The FAF bit is clear. Both the AFM counter and the TAE counters can only be incremented internally by the PCD5013 and can only be decremented by the host via AFM packet. Neither the TAE counters nor the AFM counter can be incremented past the value 127 (it does not roll-over) or decremented past the value 0. The TAE counters and the AFM counter are cleared on a reset and when the decoder is turned off. DAF: decrement all frame mode counter, see Table 63. Setting this bit decrements the AFM counter by one. If a packet is sent with this bit clear, the AFM counter is not affected. Value after reset = 0. FAF: force all frame mode, see Table 63. Setting this bit forces the PCD5013 to enter AFM. If this bit is clear, the PCD5013 may or may not be in AFM depending on the status of the AFM counter and the TAE counters. This functionality may be useful in acquiring transmitted time information. Value after reset = 0. DTA: decrement temporary address enable counter, see Table 63. When a bit in this word is set, the corresponding TAE counter is decremented by one. When a bit is clear, the corresponding TAE counter is not affected. When a TAE counter reaches zero, the temporary address is disabled. Value after reset = 0. The FLEXTM protocol requires pagers to be capable of receiving data in frames other than pagers' programmed frames and frames implied by collapse values. This is achieved in the PCD5013 by all frame mode (AFM) which is required to implement the following features: * Fragmented messages (Section 8.8.6) * Temporary addresses (Section 8.8.5). The PCD5013 enters AFM automatically and when in AFM, it decodes every FLEXTM frame irrespective of whether it is a programmed frame. In AFM the PCD5013 sends a status packet with the end-of-frame (EOF) bit set at the end of every frame. In addition the host can force AFM by sending an AFM packet with the force all frame mode (FAF) bit set. The PCD5013 contains a number of counters which are used to track the number of active calls requiring AFM. These consist of an AFM counter for tracking the number of active fragmented messages and 16 temporary address enable (TAE) counters which count the number of times each temporary address has been enabled. These counters are automatically incremented when a corresponding vector is received, i.e.: * A short instruction vector indicating a temporary address has been assigned to this pager * A vector indicating a message for this pager with a format which allows fragmentation. The host must determine when no further data can be received for a message associated with a temporary address, or a fragmented message, and send an AFM packet, see Table 63, to decrement the appropriate counter. Table 63 All frame mode packet bit assignments BYTE 3 2 1 0 BIT 7 0 DAF DTA15 DTA7 BIT 6 0 FAF DTA14 DTA6 BIT 5 0 0 DTA13 DTA5 BIT 4 0 0 DTA12 DTA4 BIT 3 0 0 DTA11 DTA3 BIT 2 0 0 DTA10 DTA2 BIT 1 1 0 DTA9 DTA1 BIT 0 1 0 DTA8 DTA0 1999 Apr 12 57 Philips Semiconductors Product specification FLEXTM roaming decoder II 8.8.5 TEMPORARY ADDRESSES PCD5013 3. The host examines the vector packet to identify which TA is assigned and the frame in which the TA is expected. 4. The PCD5013 continues to decode all of the frames and passes any address information, vector information and message information to the host followed by a status packet indicating the end of each frame and the current frame number. 5. The host processes data packets received while the PCD5013 is in AFM. It uses the AFM packet to decrement the appropriate TA counter when no further data can be expected for the corresponding TA. This occurs when: a) The TA is not found in the assigned frame. b) The TA is found in the frame it was assigned and was not a fragmented message. c) The TA is found in the assigned frame was a fragmented message and the rules for message fragmentation (Section 8.8.6) indicate that no further data can be expected. In this case the host must send an AFM packet with both the DAF and the appropriate DTA bits set in order to terminate both the fragmented message and the TA. 6. The above operation is repeated for every enabled TA. FLEXTM allows dynamic group calls in which a common message is sent to a group of paging devices. This is achieved by assigning the same temporary address (TA) to each pager in the group using the pagers' personal addresses and the short instruction vector. The short instruction vector causes the TA to be active in the next occurrence of a specific frame (if the designated frame is equal to the present frame the host is to interpret this as the next occurrence of this frame in the following cycle). FLEXTM specifies sixteen TAs which remain valid for one message starting in the specified frame and remaining valid throughout the following frames to the completion of the message. The FLEXTM protocol restricts the placement of TAs such that once assigned to a specific frame they cannot occur in the FLEXTM transmission before that frame. The PCD5013 uses AFM (Section 8.8.4) to allow the reception of TAs outside programmed frames. The sequence for the host and the PCD5013 to operate a TA is: 1. The PCD5013 receives an address codeword followed by a vector codeword with V2V1V0 = 001 and I2I1I0 = 000 indicating a short instruction vector which assigns a TA to this pager. 2. The PCD5013 passes the address and vector codeword to the host as packets and increments the corresponding TA counter and enters AFM. 1999 Apr 12 58 Philips Semiconductors Product specification FLEXTM roaming decoder II 8.8.6 MESSAGE FRAGMENTATION PCD5013 If the fragmented message was received on a temporary address, then the appropriate DTA bit should also be set in the AFM packet. b) If this is the first fragment of a fragmented message (C is set and no fragmented messages are in progress for this address and message number), then the host does not decrement the AFM counter and expects further fragments to be received for this address in subsequent frames. c) If this is the second or subsequent fragment of a fragmented message and further fragments will follow, (C is set and a fragmented message is in progress for this address and message number), then the host decrements the AFM counter by sending an AFM packet to the PCD5013 with the DAF bit set. d) If this is the last fragment of a fragmented message, (C is clear and a fragmented message is in progress for this address and message number), then the host decrements the AFM counter by 2, sending 2 AFM packets to the PCD5013 with the DAF bit set. If the fragmented message was received on a TA, then one of these AFM packets should also have the appropriate DTA bit set. 4. If, on receiving a status packet, the host determines that more than 32 or 128 frames have elapsed since the reception of a fragment for a fragmented message then the host decrements the AFM counter by sending an AFM packet to the PCD5013 with the DAF bit set. If the fragmented message was received on a TA, then the appropriate DTA bit should also be set in the AFM packet. 5. When no fragmented messages are in progress (the AFM counter = 0) and no TAs are pending (all TA counters = 0) and the FAF bit is clear in the AFM packet, the PCD5013 leaves AFM. As an alternative to the above scheme, the host may choose to decrement the AFM counter at the end of the entire message by decrementing it once for each fragment received. This method is limited to a maximum of 127 fragments. Tables 64 and 65 show examples of message reception with and without message fragmentation. The FLEXTM frame length limits the maximum number of message codewords that can be associated with an address codeword. Messages longer than 84 codewords must be sent as several fragments. The PCD5013 uses AFM (Section 8.8.4) to allow the reception of fragmented messages. The fragments of a message are sent in sequence. Each fragment contains a checksum character to detect errors in the fragment, a message number to identify which message the fragment is a part, and the continue bit which either indicates that more fragments are in queue or that the last fragment has been received. Each fragment also contains a fragment number starting with 3 for the first fragment and then incremented through the sequence 0, 1 or 2 in subsequent fragments. This allows the detection of missing fragments. Message fragments may not be separated by more than 32 frames (1 minute) or 128 frames (4 minutes), as indicated by the service provider. During the reception of a fragmented message, the PCD5013 examines every frame for additional fragments until the last fragment is encountered or the host determines that more than 32 or 128 frames have elapsed since the reception of the previous message fragment. The sequence for the host and the PCD5013 to receive a fragmented message is as follows: 1. The PCD5013 receives an address codeword followed by a vector indicating one of: a) Secure (vector type = 000) b) Alphanumeric (vector type = 101) c) Hexadecimal/binary (vector type = 110). The PCD5013 passes the address, vector and message codewords to the host as packets and increments its internal AFM counter and enters AFM. 2. While in AFM, the PCD5013 decodes all of the frames passing any address, vector and message information to the host followed by a status packet indicating the end of each frame and the current frame number. 3. Every time the host receives a secure, alphanumeric or hexadecimal/binary vector packet, it inspects the message continued flag (C) in the first message packet: a) If this is not a fragmented message (C is clear and no fragmented messages are in progress for this address and message number), then the host decrements the AFM counter by sending an AFM packet to the PCD5013 with the DAF bit set. 1999 Apr 12 59 Philips Semiconductors Product specification FLEXTM roaming decoder II Table 64 Alphanumeric message without fragmentation PACKET PHASE NUMBER 1st 2nd 3rd 4th TYPE address 1 vector 1 message AFM A A A AFM COUNTER 0 1 1 0 address 1 is received vector = alphanumeric type COMMENT PCD5013 message word received; C bit = 0; no more fragments are expected host writes AFM packet to the PCD5013 with the DAF bit = 1 Table 65 Alphanumeric message with fragmentation PACKET PHASE NUMBER 1st 2nd 3rd 4th 5th 6th 7th 8th 9th 10th 11th 12th 13th 14th TYPE address 1 vector 1 message status address 1 vector 1 message AFM status address 1 vector 1 message AFM AFM A A A B B B A A A AFM COUNTER 0 1 1 1 1 2 2 1 1 1 2 2 1 0 address 1 is received vector = alphanumeric type message word received; C bit = 1; message is fragmented, more expected end of frame indication (EOF = 1) address 1 is received vector = alphanumeric type message word received; C bit = 1; message is fragmented, more expected host writes AFM packet to the PCD5013 with the DAF bit = 1 end of frame indication (EOF = 1) address 1 is received vector = alphanumeric type message word received; C bit = 0; no more fragments are expected host writes AFM packet to the PCD5013 with the DAF bit = 1 host writes AFM packet to the PCD5013 with the DAF bit = 1 COMMENT 1999 Apr 12 60 Philips Semiconductors Product specification FLEXTM roaming decoder II 8.8.6.1 Fragmentation of non-7-bit character sets PCD5013 codeword are added to form a binary sum. The message checksum is the 1's complement of the LSBs of the binary sum, where the number of bits taken is determined by the message type (Section 8.7.8). In the case of the 6-bit message checksum used in numeric messages, a binary sum is first calculated as described above. The binary sum is then truncated to its 8 LSBs, then the 2 MSBs are shifted right by 6 bits and added to the least significant 6 bits to form a new binary sum. The 6 LSBs of this new sum are taken and 1's complemented to form the 6-bit message checksum. 8.8.8 MESSAGE NUMBERING FLEXTM alphanumeric messages can be used to send symbolic characters like Chinese, Kanji, etc. In this case several ASCII characters are used to represent each symbolic character. Enhanced fragmentation (EF) rules are provided by FLEXTM to allow character positions within a fragment to be determined in the event of missing fragments under poor signal conditions. 1. The pager must remove FLEXTM messages may be numbered (Section 8.7.8), in this case the system controller assigns message numbers (for each paging address separately) starting at 0 and progressing up to a maximum of 63 in numerical order. The maximum roll-over number is defined in the pager code plug to accommodate values set in the system infrastructure. When message numbers are not received in order, the subscriber should assume a message has been missed. When a message number is missed, the subscriber or the pager may determine the missing message number(s) allowing a request to be made for retrieval. Messages which can be received out of sequence are indicated by clearing the message retrieval flag R. Messages with R cleared number should not be included in the missed message calculation. In case of fragmented messages, this number is also used to identify fragments of the same message. Multiple messages to the same address must have separate message numbers. Table 66 Fragmentation control bit definitions U0 0 0 1 1 V0 0 1 0 1 DEFINITION EF not supported in controller reserved (for a second alternate character mode) default character mode start position 1 alternate character mode start position 1 FLEXTM provides a message checksum facility for alphanumeric, numeric, hex/binary, and secure messages. The checksum is calculated by summing the information bits of each codeword in the message or message fragment (including control information and termination characters and bits in the last message codeword). Information bits of each codeword are broken into three groups as indicated in Table 67. Bits i0, i8 and i16 are the LSBs of each group and bit i0 is the first bit of the codeword to be transmitted. The 3 groups are for each Table 67 Bit groups for message checksums i0 i1 i2 i3 i4 i5 i6 i7 i8 i9 i10 i11 i12 i13 i14 i15 i16 i17 i18 group 3 i19 i20 group 1 group 2 1999 Apr 12 61 Philips Semiconductors Product specification FLEXTM roaming decoder II 8.8.9 USING THE RECEIVER SHUTDOWN PACKET PCD5013 This can occur either because the pager has entered a new area or because the Roaming IDs or Traffic Management Flags change. A pager can stop monitoring a channel either because the channel's Roaming ID changes or because no signal has been encountered on the channel for a given period. When all the monitored channels have been lost, the pager must start a global scan. The PCD5013 sends information to the host in the Receiver Shutdown Packet (see Section 8.4.12) every time it shuts the receiver down. This allows the host to calculate whether it will have enough time to switch frequencies before the receiver next switches on (see Section 8.8.9.2). The PCD5013 allows the identification of Roaming IDs by the support for the reception of SSID Block Information words and Short Messaging Vectors (see Sections 8.7.5 and 8.7.9) 8.8.9.1 Operation of Roaming features A roaming pager scans channels in a frequency list to determine the channel or channels to monitor. The pager matches the Roaming IDs (SSIDs, NIDs or any IDs) transmitted on monitored channels against those contained in the pager's Roaming ID list. Each item in the Roaming ID list is assigned a priority to ensure determinative behaviour for roaming pagers. Implementation of a Roaming Pager using the PCD5013 is greatly simplified using the FLEXTM software. Items in the Roaming ID list are assigned priorities to arbitrate in the case where a pager is in a coverage in which there is more than one RF channel. In the case that a pager receives data from two channels both of Roaming Identifiers of the highest priority, it can enter one of two modes of operation (as determined by the pager programming). Channel scanning is done to determine whether to switch channel because there is a channel of higher priority than the currently monitored channel. * Global scanning: the scan of all RF channels after switch on. Once the global scan is completed, the pager starts to monitor all channels with a programmed priority which is equal to or higher than the highest priority channel on which a FLEXTM transmission was encountered. If no FLEXTM transmission is encountered the pager must restart the global scan after some battery saving period. * Background scanning: scanning done to determine whether the pager one of the monitored RF channels carries a FLEXTM signal with higher priority than the currently monitored channel. Synchronous mode: 8.8.9.2 Calculating time left The receiver shutdown packet gives timing information to the host. Two times are of particular interest when implementing a roaming algorithm. TimeToWarmUpStart: Defined as the amount of time there is before the receiver starts to warm-up (i.e. transition from the off state to the first warm-up state). TimeToTasksDisabled: Defined as the amount of time the host has to complete any host initiated tasks (e.g. by setting SND or SAS in the roaming control packet). The formulae for calculating these times are shown below and depend on whether the PCD5013 is in Synchronous mode or Asynchronous mode. TimeToWarmupStart ( TNF x 80 ms ) + ( SkippedFrames x 1874.375 ms ) + ( ReceiverOffTime - 167.5 ms ) TimeToTasksDisabled ( TNF x 80 ms ) + ( SkippedFrames x 1874.375 ms ) + ( ReceiverOffTime - 247.5 ms ) Asynchronous mode: TimeToWarmupStart [ ( TNF - 2 ) x 80 ms ] + ReceiverOffTime TimeToTasksDisabled [ ( TNF - 3 ) x 80 ms ] Where: TNF (Time to Next Frame): value from the receiver shutdown packet. SkippedFrames: the number of frames that will not be decoded. Calculated from the Current Frame (CF) and Next Needed Frame (NAF) fields in the receiver shutdown packet (e.g. if CF is 10 and NAF is 12, then SkippedFrames is 1). ReceiverOffTime: the time programmed in the receiver off setting packet. 1999 Apr 12 62 Philips Semiconductors Product specification FLEXTM roaming decoder II 8.8.9.3 Calculating how long tasks take PCD5013 Equation (1) calculates how long it takes to complete a Noise Detect started by setting the SND bit in the roaming control packet. This formula assumes that: * the noise detect was performed while in synchronous mode OR * the noise detect was performed in asynchronous mode and did not find FLEXTM signal OR * the noise detect found FLEXTM signal but the DAS bit of the roaming control packet was set. Equation (2) calculates how long it will take to complete an A-word search initiated by setting the SAS bit in the roaming control packet. This formula assumes that the A-word search failed to find roaming FLEXTM channel. Equation (3) calculates how long it will take to complete a Noise Detect/A-word search combination. This can occur when the noise detect is performed while in asynchronous mode, the noise detect finds FLEXTM signal, and the DAS bit of the roaming control packet is not set. (1) (2) (3) Since the TimeToTaskDisabled discussed in the previous section limits how much the host can do while the PCD5013 is battery saving, it is necessary for the host to know how long it can take the PCD5013 to perform a task. The formulae below calculate how long the two types of host initiated tasks take to complete as measured from the last SPI clock of the packet that initiates the task to the time the receiver shutdown sequence starts. Note that the receiver shutdown sequence must start before tasks are disabled.The following definitions are used: TotalWarmUpTime: The sum of the times programmed for the used warm-up steps plus the time programmed for the 3200 sps Sync Setting in the receiver control configuration packets AST: The value configured using the timing control packet. TimeToPerformNoiseDetect TotalWarmUpTime + 82 ms TimeToPerformAwordSearch TotalWarmupTime + AST + 47 ms TimeToPerformBoth TotalWarmUpTime + AST + 127 ms 1999 Apr 12 63 Philips Semiconductors Product specification FLEXTM roaming decoder II 9 LIMITING VALUES In accordance with the absolute maximum rating system (IEC 134). SYMBOL VDD IDD II IO VI Ptot PO Tamb Tstg Notes 1. VDD1 and VDD2 respectively and VSS1 and VSS2 must be connected at the same potential. 2. VI(max) = 4.0 V. 10 HANDLING PARAMETER supply voltage supply current DC input current (any input) DC output current (any output) input voltages (all inputs) total power dissipation power dissipation per output operating ambient temperature storage temperature note 2 CONDITIONS note 1 -0.5 - -10 -10 -0.5 - - -25 -65 MIN. 4.0 50 +10 +10 VDD + 0.5 300 10 +70 +150 MAX. PCD5013 UNIT V mA mA mA V mW mW C C Inputs and outputs are protected against electrostatic discharge in normal handling. However, to be totally safe, it is desirable to take normal precautions appropriate to handling MOS devices. 11 THERMAL CHARACTERISTICS SYMBOL Rth(j-a) PARAMETER CONDITIONS VALUE 90 UNIT K/W thermal resistance from junction to ambient in free air 1999 Apr 12 64 Philips Semiconductors Product specification FLEXTM roaming decoder II 12 DC CHARACTERISTICS Tamb = -25 to +70 C; VDD = 2.2 V; f = 76.8 kHz; unless otherwise specified. SYMBOL Supply VDD IDD(stby) IDD VIL VIH ILI VOL VOH ILO Notes supply voltage standby supply current operating supply current on = 0; note 1 on = 1; note 2 1.8 - - - 0.8VDD - - - 2.2 4.9 6.0 - - - 3.6 24 - PARAMETER CONDITIONS MIN. TYP. PCD5013 MAX. UNIT V A A Digital inputs: OSCPD, TEST2, TEST3, RESET, LOBAT, EXTS0, EXTS1, SS and MOSI LOW-level input voltage HIGH-level input voltage LOW/HIGH-level input leakage current 0.2VDD - 1 V V A Digital outputs: MISO, READY, CLKOUT, SYMCLK and S0 to S7 LOW-level output voltage HIGH-level output voltage Isink = 0.8 mA Isource = -0.8 mA 0.1 - 0.4 1 V V A VDD - 0.4 VDD - 0.1 - LOW/HIGH-level output leakage current 3-state outputs 1. External clock signal (frequency = 76.8 kHz, amplitude = VSS to VDD) at pin EXTAL; OSCPD = HIGH; test inputs = LOW; other inputs = HIGH; outputs unconnected; SPI transmit enabled; COD bit set to logic 1 (see Section 8.4.4); to obtain the supply current of an application with a crystal connected as in Fig.19, a typical oscillator current of 2 A needs to be added to this value (see Chapter 14); Tamb = 25 C. 2. As note 1, but PCD5013 and synchronous to a typical FLEXTM data stream (collapse value = 4), Tamb = 25 C. 13 AC CHARACTERISTICS Tamb = -25 to +70 C, VDD = 1.8 to 3.6 V, fEXTAL = 76.8 kHz, maximum load capacitance = 50 pF connected to any digital output; unless otherwise specified. SYMBOL Reset timing tW(rst) tLH(RESET-READY) tHL(RESET-READY) Start-up timing tstrt(osc) th(rst) tHL(RESET-READY) tWUL(osc-READY) SPI timing fSCK Tcy(SCK) tLEAD1 tLAG1 1999 Apr 12 operating frequency cycle time select lead time de-select lag time 65 0 1000 200 200 - - - - 1 - - - MHz ns ns ns oscillator start-up time RESET hold time RESET HIGH to READY LOW note 1 oscillator warmed up to READY LOW note 1 see Fig.19 - 200 - - 0.5 - - - s ns T T RESET pulse width RESET LOW to READY HIGH RESET HIGH to READY LOW stable 76.8 kHz clock 200 - - - - 1 - 200 - ns ns s PARAMETER CONDITIONS MIN. TYP. MAX. UNIT 76800 - 76800 - Philips Semiconductors Product specification FLEXTM roaming decoder II PCD5013 SYMBOL td(SS-READY) PARAMETER SS-to-READY delay time CONDITIONS MIN. TYP. - - - - - - - - - - - - - - - - MAX. 80 420 - - 200 - - 200 300 200 - - - - 1 1 UNIT s s s ns ns ns ns ns ns ns ns ns ns ns s s previous packet did not program - an address word; note 2 previous packet programmed an address word; note 2 - 50 200 - 200 200 0 - - 0 200 300 200 10% to 90% VDD 10% to 90% VDD - - tREADYH tLEAD2 tLAG2 tsu(i)(D) th(i)(D) tACC(o) to(dis) tDOV th(o)(D) tSSH tSCKH tSCKL tr tf Notes READY HIGH time READY lead time READY lag time MOSI data setup time MOSI data hold time MISO access time MISO disable time MISO data valid time MISO data hold time SS HIGH time SCK HIGH time SCK LOW time SCK rise time SCK fall time 1. T is one period of the clock source either generated by the internal oscillator, or applied at the input EXTAL. Note that from power-up, the oscillator start-up time can influence the availability and period of clock strobes. This can affect the RESET HIGH to READY LOW timing. 2. When the host re-programs an address word with a host-to-decoder packet ID > 7FH, there is an added delay before the PCD5013 is ready for another packet. 14 OSCILLATOR CHARACTERISTICS Tamb = -25 to +70 C; note 1. SYMBOL C1 C2 Rf gm(osc) Iosc Notes 1. Designed for quartz crystal type: SEIKO VTC200 or equivalent; parameters: f = 76800Hz, RS = 35 k (max.), CL = C1.C2/(C1 + C2) + Cstray = 8 to 12 pF, C0 = crystal shunt capacitance = 0.8 pF (typ.), Cf = typical parasitic pin capacitance = 2 pF; maximum overall frequency tolerance (including transmitter) is 300 ppm (Section 8.4.4). 2. Extracted from evaluations under conditions as in Fig.19; this value is strongly dependent on external conditions (load and parasitic capacitances). PARAMETER external capacitor at pin EXTAL external capacitor at pin XTAL external feedback resistor oscillator transconductance oscillator operating supply current VDD = 2.2 V; note 2 CONDITIONS note 1 note 1 note 1 MIN. - - - 9.4 - TYP. 15 15 10 27 2 MAX. - - - 70 - UNIT pF pF M S A 1999 Apr 12 66 Philips Semiconductors Product specification FLEXTM roaming decoder II 15 TEST AND APPLICATION INFORMATION 15.1 FLEXTM protocol PCD5013 Please note that the issuing of this document is not part of the "FLEXTM Total Messaging Solution" agreement. Enquiries about the FLEXTM protocol not covered by the "FLEXTM Total Messaging Solution" should be directed to: Motorola Inc. FLEXTM Licensing Manager, Mail Stop 99, 1500 Gateway Boulevard, Boynton Beach, Florida 33426. FAX: (561) 739-2519 Telephone: (561) 739-8281. The PCD5013 conveys a licence to manufacture Pagers using the "FLEXTM Total Messaging Solution" agreement. For the terms and conditions of this agreement please contact Philips Semiconductors. Further details of the FLEXTM protocol are contained in the document "FLEXTM Protocol and FLEXTM Encoding and Decoding Requirements". 15.2 Example applications handbook, full pagewidth Vsup DC/DC CONVERTER 10 F 100 nF VDD1, VDD2 VDD 3 OSCPD, TEST2, TEST3 SYMCLK CLKOUT RECEIVER FRONT-END KEYPAD READY, SS, SCK, MOSI, MISO 5 MICROCONTROLLER P87CL881 PCD5013 S0 to S7 IF AND 4-LEVEL DEMODULATOR 8 EXTS0, EXTS1 2 LOBAT EXTAL RESET TOUT0 to TOUT3 4 76.8 kHz XTAL 2 VSS1, VSS2 I2C-bus EEPROM LCD DRIVER LCD MGR621 10 M 15 pF 15 pF Fig.19 Example application using external demodulation. 1999 Apr 12 67 Philips Semiconductors Product specification FLEXTM roaming decoder II PCD5013 handbook, full pagewidth Vsup DC/DC CONVERTER 10 F 100 nF VDD1, VDD2 VDD 3 OSCPD, TEST2, TEST3 SYMCLK CLKOUT RECEIVER FRONT-END KEYPAD READY, SS, SCK, MOSI, MISO 5 MICROCONTROLLER P87CL881 PCD5013 S1 to S7 8 S0/IFIN LOBAT RESET IF TOUT0 to TOUT3 4 EXTAL 160 kHz XTAL 2 VSS1, VSS2 I2C-bus EEPROM LCD DRIVER LCD MGR622 10 M 15 pF 15 pF Fig.20 Example application using internal demodulator. 1999 Apr 12 68 Philips Semiconductors Product specification FLEXTM roaming decoder II 15.3 System block diagram PCD5013 handbook, full pagewidth BATTERY LOW DETECTOR PAGING RECEIVER receiver control lines RF RECEIVER 7 battery low indication HOST MICROPROCESSOR reset USER INTERFACE PCD5013 455 kHz IF data IF BACKEND 1 API serial peripheral interface 5 FLEXstackTM SOFTWARE SPI INTERFACE MGR620 160 kHz crystal Fig.21 System block diagram. 1999 Apr 12 69 Philips Semiconductors Product specification FLEXTM roaming decoder II 16 PACKAGE OUTLINE LQFP32: plastic low profile quad flat package; 32 leads; body 7 x 7 x 1.4 mm PCD5013 SOT358-1 c y X 24 25 17 16 ZE A e E HE wM bp pin 1 index 32 1 e bp D HD wM B vM B 8 ZD vM A 9 detail X L Lp A A2 A 1 (A 3) 0 2.5 scale 5 mm DIMENSIONS (mm are the original dimensions) UNIT mm A max. 1.60 A1 0.20 0.05 A2 1.45 1.35 A3 0.25 bp 0.4 0.3 c 0.18 0.12 D (1) 7.1 6.9 E (1) 7.1 6.9 e 0.8 HD 9.15 8.85 HE 9.15 8.85 L 1.0 Lp 0.75 0.45 v 0.2 w 0.25 y 0.1 Z D (1) Z E (1) 0.9 0.5 0.9 0.5 7 0o o Note 1. Plastic or metal protrusions of 0.25 mm maximum per side are not included. OUTLINE VERSION SOT358 -1 REFERENCES IEC JEDEC EIAJ EUROPEAN PROJECTION ISSUE DATE 95-12-19 97-08-04 1999 Apr 12 70 Philips Semiconductors Product specification FLEXTM roaming decoder II 17 SOLDERING 17.1 Introduction to soldering surface mount packages PCD5013 * Use a double-wave soldering method comprising a turbulent wave with high upward pressure followed by a smooth laminar wave. * For packages with leads on two sides and a pitch (e): - larger than or equal to 1.27 mm, the footprint longitudinal axis is preferred to be parallel to the transport direction of the printed-circuit board; - smaller than 1.27 mm, the footprint longitudinal axis must be parallel to the transport direction of the printed-circuit board. The footprint must incorporate solder thieves at the downstream end. * For packages with leads on four sides, the footprint must be placed at a 45 angle to the transport direction of the printed-circuit board. The footprint must incorporate solder thieves downstream and at the side corners. During placement and before soldering, the package must be fixed with a droplet of adhesive. The adhesive can be applied by screen printing, pin transfer or syringe dispensing. The package can be soldered after the adhesive is cured. Typical dwell time is 4 seconds at 250 C. A mildly-activated flux will eliminate the need for removal of corrosive residues in most applications. 17.4 Manual soldering This text gives a very brief insight to a complex technology. A more in-depth account of soldering ICs can be found in our "Data Handbook IC26; Integrated Circuit Packages" (document order number 9398 652 90011). There is no soldering method that is ideal for all surface mount IC packages. Wave soldering is not always suitable for surface mount ICs, or for printed-circuit boards with high population densities. In these situations reflow soldering is often used. 17.2 Reflow soldering Reflow soldering requires solder paste (a suspension of fine solder particles, flux and binding agent) to be applied to the printed-circuit board by screen printing, stencilling or pressure-syringe dispensing before package placement. Several methods exist for reflowing; for example, infrared/convection heating in a conveyor type oven. Throughput times (preheating, soldering and cooling) vary between 100 and 200 seconds depending on heating method. Typical reflow peak temperatures range from 215 to 250 C. The top-surface temperature of the packages should preferable be kept below 230 C. 17.3 Wave soldering Conventional single wave soldering is not recommended for surface mount devices (SMDs) or printed-circuit boards with a high component density, as solder bridging and non-wetting can present major problems. To overcome these problems the double-wave soldering method was specifically developed. If wave soldering is used the following conditions must be observed for optimal results: Fix the component by first soldering two diagonally-opposite end leads. Use a low voltage (24 V or less) soldering iron applied to the flat part of the lead. Contact time must be limited to 10 seconds at up to 300 C. When using a dedicated tool, all other leads can be soldered in one operation within 2 to 5 seconds between 270 and 320 C. 1999 Apr 12 71 Philips Semiconductors Product specification FLEXTM roaming decoder II 17.5 Suitability of surface mount IC packages for wave and reflow soldering methods SOLDERING METHOD PACKAGE WAVE BGA, SQFP PLCC(3), SO, SOJ not suitable suitable(2) suitable not recommended(3)(4) not recommended(5) suitable suitable suitable suitable suitable HLQFP, HSQFP, HSOP, HTSSOP, SMS not LQFP, QFP, TQFP SSOP, TSSOP, VSO Notes PCD5013 REFLOW(1) 1. All surface mount (SMD) packages are moisture sensitive. Depending upon the moisture content, the maximum temperature (with respect to time) and body size of the package, there is a risk that internal or external package cracks may occur due to vaporization of the moisture in them (the so called popcorn effect). For details, refer to the Drypack information in the "Data Handbook IC26; Integrated Circuit Packages; Section: Packing Methods". 2. These packages are not suitable for wave soldering as a solder joint between the printed-circuit board and heatsink (at bottom version) can not be achieved, and as solder may stick to the heatsink (on top version). 3. If wave soldering is considered, then the package must be placed at a 45 angle to the solder wave direction. The package footprint must incorporate solder thieves downstream and at the side corners. 4. Wave soldering is only suitable for LQFP, TQFP and QFP packages with a pitch (e) equal to or larger than 0.8 mm; it is definitely not suitable for packages with a pitch (e) equal to or smaller than 0.65 mm. 5. Wave soldering is only suitable for SSOP and TSSOP packages with a pitch (e) equal to or larger than 0.65 mm; it is definitely not suitable for packages with a pitch (e) equal to or smaller than 0.5 mm. 1999 Apr 12 72 Philips Semiconductors Product specification FLEXTM roaming decoder II 18 DEFINITIONS Data sheet status Objective specification Preliminary specification Product specification Limiting values PCD5013 This data sheet contains target or goal specifications for product development. This data sheet contains preliminary data; supplementary data may be published later. This data sheet contains final product specifications. Limiting values given are in accordance with the Absolute Maximum Rating System (IEC 134). Stress above one or more of the limiting values may cause permanent damage to the device. These are stress ratings only and operation of the device at these or at any other conditions above those given in the Characteristics sections of the specification is not implied. Exposure to limiting values for extended periods may affect device reliability. Application information Where application information is given, it is advisory and does not form part of the specification. 19 LIFE SUPPORT APPLICATIONS These products are not designed for use in life support appliances, devices, or systems where malfunction of these products can reasonably be expected to result in personal injury. Philips customers using or selling these products for use in such applications do so at their own risk and agree to fully indemnify Philips for any damages resulting from such improper use or sale. 1999 Apr 12 73 Philips Semiconductors Product specification FLEXTM roaming decoder II NOTES PCD5013 1999 Apr 12 74 Philips Semiconductors Product specification FLEXTM roaming decoder II NOTES PCD5013 1999 Apr 12 75 Philips Semiconductors - a worldwide company Argentina: see South America Australia: 34 Waterloo Road, NORTH RYDE, NSW 2113, Tel. +61 2 9805 4455, Fax. +61 2 9805 4466 Austria: Computerstr. 6, A-1101 WIEN, P.O. Box 213, Tel. +43 1 60 101 1248, Fax. +43 1 60 101 1210 Belarus: Hotel Minsk Business Center, Bld. 3, r. 1211, Volodarski Str. 6, 220050 MINSK, Tel. +375 172 20 0733, Fax. +375 172 20 0773 Belgium: see The Netherlands Brazil: see South America Bulgaria: Philips Bulgaria Ltd., Energoproject, 15th floor, 51 James Bourchier Blvd., 1407 SOFIA, Tel. +359 2 68 9211, Fax. +359 2 68 9102 Canada: PHILIPS SEMICONDUCTORS/COMPONENTS, Tel. +1 800 234 7381, Fax. +1 800 943 0087 China/Hong Kong: 501 Hong Kong Industrial Technology Centre, 72 Tat Chee Avenue, Kowloon Tong, HONG KONG, Tel. +852 2319 7888, Fax. +852 2319 7700 Colombia: see South America Czech Republic: see Austria Denmark: Sydhavnsgade 23, 1780 COPENHAGEN V, Tel. +45 33 29 3333, Fax. +45 33 29 3905 Finland: Sinikalliontie 3, FIN-02630 ESPOO, Tel. +358 9 615 800, Fax. +358 9 6158 0920 France: 51 Rue Carnot, BP317, 92156 SURESNES Cedex, Tel. +33 1 4099 6161, Fax. +33 1 4099 6427 Germany: Hammerbrookstrae 69, D-20097 HAMBURG, Tel. +49 40 2353 60, Fax. +49 40 2353 6300 Hungary: see Austria India: Philips INDIA Ltd, Band Box Building, 2nd floor, 254-D, Dr. Annie Besant Road, Worli, MUMBAI 400 025, Tel. +91 22 493 8541, Fax. +91 22 493 0966 Indonesia: PT Philips Development Corporation, Semiconductors Division, Gedung Philips, Jl. Buncit Raya Kav.99-100, JAKARTA 12510, Tel. +62 21 794 0040 ext. 2501, Fax. +62 21 794 0080 Ireland: Newstead, Clonskeagh, DUBLIN 14, Tel. +353 1 7640 000, Fax. +353 1 7640 200 Israel: RAPAC Electronics, 7 Kehilat Saloniki St, PO Box 18053, TEL AVIV 61180, Tel. +972 3 645 0444, Fax. +972 3 649 1007 Italy: PHILIPS SEMICONDUCTORS, Piazza IV Novembre 3, 20124 MILANO, Tel. +39 2 6752 2531, Fax. +39 2 6752 2557 Japan: Philips Bldg 13-37, Kohnan 2-chome, Minato-ku, TOKYO 108-8507, Tel. +81 3 3740 5130, Fax. +81 3 3740 5077 Korea: Philips House, 260-199 Itaewon-dong, Yongsan-ku, SEOUL, Tel. +82 2 709 1412, Fax. +82 2 709 1415 Malaysia: No. 76 Jalan Universiti, 46200 PETALING JAYA, SELANGOR, Tel. +60 3 750 5214, Fax. +60 3 757 4880 Mexico: 5900 Gateway East, Suite 200, EL PASO, TEXAS 79905, Tel. +9-5 800 234 7381, Fax +9-5 800 943 0087 Middle East: see Italy Netherlands: Postbus 90050, 5600 PB EINDHOVEN, Bldg. VB, Tel. +31 40 27 82785, Fax. +31 40 27 88399 New Zealand: 2 Wagener Place, C.P.O. Box 1041, AUCKLAND, Tel. +64 9 849 4160, Fax. +64 9 849 7811 Norway: Box 1, Manglerud 0612, OSLO, Tel. +47 22 74 8000, Fax. +47 22 74 8341 Pakistan: see Singapore Philippines: Philips Semiconductors Philippines Inc., 106 Valero St. Salcedo Village, P.O. Box 2108 MCC, MAKATI, Metro MANILA, Tel. +63 2 816 6380, Fax. +63 2 817 3474 Poland: Ul. Lukiska 10, PL 04-123 WARSZAWA, Tel. +48 22 612 2831, Fax. +48 22 612 2327 Portugal: see Spain Romania: see Italy Russia: Philips Russia, Ul. Usatcheva 35A, 119048 MOSCOW, Tel. +7 095 755 6918, Fax. +7 095 755 6919 Singapore: Lorong 1, Toa Payoh, SINGAPORE 319762, Tel. +65 350 2538, Fax. +65 251 6500 Slovakia: see Austria Slovenia: see Italy South Africa: S.A. PHILIPS Pty Ltd., 195-215 Main Road Martindale, 2092 JOHANNESBURG, P.O. Box 7430 Johannesburg 2000, Tel. +27 11 470 5911, Fax. +27 11 470 5494 South America: Al. Vicente Pinzon, 173, 6th floor, 04547-130 SAO PAULO, SP, Brazil, Tel. +55 11 821 2333, Fax. +55 11 821 2382 Spain: Balmes 22, 08007 BARCELONA, Tel. +34 93 301 6312, Fax. +34 93 301 4107 Sweden: Kottbygatan 7, Akalla, S-16485 STOCKHOLM, Tel. +46 8 5985 2000, Fax. +46 8 5985 2745 Switzerland: Allmendstrasse 140, CH-8027 ZURICH, Tel. +41 1 488 2741 Fax. +41 1 488 3263 Taiwan: Philips Semiconductors, 6F, No. 96, Chien Kuo N. Rd., Sec. 1, TAIPEI, Taiwan Tel. +886 2 2134 2886, Fax. +886 2 2134 2874 Thailand: PHILIPS ELECTRONICS (THAILAND) Ltd., 209/2 Sanpavuth-Bangna Road Prakanong, BANGKOK 10260, Tel. +66 2 745 4090, Fax. +66 2 398 0793 Turkey: Talatpasa Cad. No. 5, 80640 GULTEPE/ISTANBUL, Tel. +90 212 279 2770, Fax. +90 212 282 6707 Ukraine: PHILIPS UKRAINE, 4 Patrice Lumumba str., Building B, Floor 7, 252042 KIEV, Tel. +380 44 264 2776, Fax. +380 44 268 0461 United Kingdom: Philips Semiconductors Ltd., 276 Bath Road, Hayes, MIDDLESEX UB3 5BX, Tel. +44 181 730 5000, Fax. +44 181 754 8421 United States: 811 East Arques Avenue, SUNNYVALE, CA 94088-3409, Tel. +1 800 234 7381, Fax. +1 800 943 0087 Uruguay: see South America Vietnam: see Singapore Yugoslavia: PHILIPS, Trg N. Pasica 5/v, 11000 BEOGRAD, Tel. +381 11 62 5344, Fax.+381 11 63 5777 For all other countries apply to: Philips Semiconductors, International Marketing & Sales Communications, Building BE-p, P.O. Box 218, 5600 MD EINDHOVEN, The Netherlands, Fax. +31 40 27 24825 (c) Philips Electronics N.V. 1999 Internet: http://www.semiconductors.philips.com SCA63 All rights are reserved. Reproduction in whole or in part is prohibited without the prior written consent of the copyright owner. The information presented in this document does not form part of any quotation or contract, is believed to be accurate and reliable and may be changed without notice. No liability will be accepted by the publisher for any consequence of its use. Publication thereof does not convey nor imply any license under patent- or other industrial or intellectual property rights. Printed in The Netherlands 465008/00/02/pp76 Date of release: 1999 Apr 12 Document order number: 9397 750 05593 |
Price & Availability of PCD5013
 |
|
|
|
|
All Rights Reserved © IC-ON-LINE 2003 - 2022 |
| [Add Bookmark] [Contact Us] [Link exchange] [Privacy policy] |
|
Mirror Sites : [www.datasheet.hk]
[www.maxim4u.com] [www.ic-on-line.cn]
[www.ic-on-line.com] [www.ic-on-line.net]
[www.alldatasheet.com.cn]
[www.gdcy.com]
[www.gdcy.net] |